@kapa.ai I have just upgraded the airbyte application database from postgresql 15 to postgresql 18 and the temporal component is unable to start. It has this error in the logs:

pq: permission denied for schema public

. Any thoughts?

The

pq: permission denied for schema public

error is a known issue when connecting Airbyte to an external PostgreSQL database. Based on the knowledge sources, this is typically a permissions problem where the Airbyte database user lacks sufficient privileges on the

public

schema. One documented case shows a similar error occurring during schema setup [Docs issue]: >

ERROR: permission denied for schema public

...

CREATE INDEX IF NOT EXISTS airbyte_configs_id_idx ON AIRBYTE_CONFIGS(config_id)

The recommended fix is to ensure your Airbyte database user has full privileges on the relevant databases and schemas. Based on the knowledge sources, you should run something like the following:

-- For the temporal databases
CREATE DATABASE temporal;
GRANT ALL PRIVILEGES ON DATABASE temporal TO airbyte_user;

CREATE DATABASE temporal_visibility;
GRANT ALL PRIVILEGES ON DATABASE temporal_visibility TO airbyte_user;

-- For the public schema in each database
\c temporal
GRANT ALL PRIVILEGES ON SCHEMA public TO airbyte_user;

\c temporal_visibility
GRANT ALL PRIVILEGES ON SCHEMA public TO airbyte_user;

[Forum answer] A few additional notes from the knowledge sources: • The Temporal component requires the database user to have

CREATEDB

permissions, as it attempts to create the

temporal

and

temporal_visibility

databases if they don't exist. If those databases are pre-created, you still need to ensure the user has full schema-level privileges. [Kubernetes temporal issue] • If the databases already exist, Temporal may still fail if schema-level permissions are missing, which is consistent with the

permission denied for schema public

error you're seeing. It's worth noting that the knowledge sources do not explicitly address whether upgrading from PostgreSQL 15 to PostgreSQL 18 introduces any specific permission changes (e.g., PostgreSQL 15 changed default privileges on the

public

schema). However, the fix of explicitly granting schema privileges to your Airbyte user is the documented solution for this class of error. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.