Postgres Node Refresh Wipes Existing Expressions in n8n

Below is some background information regarding the Postgres node’s behavior when refreshing columns:

Current Behavior

When you refresh the columns in the Postgres node, any pre-set expressions in field mappings are removed. This means that if your database schema is extended, you need to manually reconfigure each expression. This differs from other nodes like the Supabase node, which retain preset expressions on refresh.

Considerations and Workarounds

• Manual Mapping: One way to reduce the disruption is to use manual mapping for each column. Although this doesn’t prevent the expressions from being removed when you refresh, it may simplify your reconfiguration process if you work with a static set of columns.
• Feature Request or Bug?
  Based on your description, it isn’t immediately clear whether the current behavior is unintended (a bug) or a design decision. However, if retaining preset expressions upon refresh is a preferred behavior—as seen in some other nodes—a feature request might be in order.

Next Steps

• Feedback and Feature Requests:
  If you feel that retaining expressions would improve usability and reduce repetitive work when updating the database schema, you may want to log this as a feature request with the n8n team. Your feedback is valuable and helps prioritize future improvements.

• Further Troubleshooting:
  While there isn’t an official workaround documented to automatically preserve expressions during a column refresh in the Postgres node, following up on the n8n community forums or GitHub repository might provide additional insights or temporary fixes contributed by the community.

Feel free to share this feedback through the appropriate channels so that the n8n team can review it for potential future updates.