Why Was the Input Schema Field Removed in n8n v1.78.0?

It turns out that nothing is “wrong” per se—instead the field was intentionally removed from the UI in favor of using the default value. In v1.78.0 the Postgres node (and accompanying credentials) now always uses the schema defined by the backend (which is "public" by default). If you need a different schema you must set it via the environment variable (DB_POSTGRESDB_SCHEMA) instead of providing it as an input to the node.

This change was made so that the UI isn’t cluttered with fields that rarely need adjustment. If you want to use a schema other than “public”, update your deployment’s configuration accordingly.

Below is an explanation that covers what’s happening and how to address it:

---

In v1.78.0 (and recent versions) the way that the schema is handled for Postgres has changed. In previous releases you might have seen an extra “input schema” field in the node dialog. However, with the newer design the default Postgres schema is taken from your credentials/environment (via the DB_POSTGRESDB_SCHEMA variable, which defaults to "public" unless changed), so the field has been removed from the node’s user interface.

What this means for you:

• If you haven’t explicitly set a custom schema in your credentials (or via the environment variable), n8n uses the default schema.
• The UI no longer shows a dedicated field for it since it is assumed you either want to use that default or manage the schema through your credentials configuration.
• If you need to work with a schema that is different from the default, update your credentials (or set the environment variable DB_POSTGRESDB_SCHEMA accordingly) rather than expecting an “input schema” field on the node.

This change is intentional so that the node focuses on the SQL operations (like select, insert, update, etc.) while relying on the preset database configuration.

---

If you need to work with a different schema than the one provided via credentials, you can modify your Postgres credentials (or set/override the environment variable) so that the node uses the proper schema throughout your workflows.