The idea is:
When I add more indices or make any other changes to my database schema, it would be useful to have a button in the postgres node that re-reads the schema so it becomes aware of any new indexes or unique keys. This is especially useful for “Insert” and “Insert or Update” operations.
My use case:
An example use case is what I’m doing right now, importing a CSV file and inserting it into a PostgreSQL table. I’m not 100% familiar with the CSV data and as I learn more about the data, I am modifying the unique keys and adding indices, but the node’s “Columns to match on” does not update the schema, even after a complete reload of the workflow. I have to delete the node and re-create it, and then I can see the new indexes.
I think it would be beneficial to add this because:
This will benefit any n8n user that needs to make changes to their db schema after a workflow has already been created.
