PostgreSQL support

Last updated date:

Connect, reconnect, and troubleshoot PostgreSQL without sharing credentials or customer content through support channels.

1. Before you start

  • Create a dedicated login with CONNECT on the exact database and USAGE only on schemas Seedling should inventory.
  • Do not grant application-table SELECT for the current catalog-only sync.
  • Choose require, verify-ca, or verify-full according to the host policy and provide the correct root CA for identity verification.
  • Do not send PostgreSQL credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
PostgreSQL privilegesPostgreSQL's privilege model documentation.

2. Connect PostgreSQL

  1. In Seedling, open Connections and choose PostgreSQL.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the host, port, database, dedicated username and password, SSL mode, and root CA certificate when verify-ca or verify-full is used.
  4. Seedling establishes the TLS connection, verifies the database identity, and reads only the released catalog and privilege queries.
  5. Allow the first PostgreSQL synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

PostgreSQL login rejected
Confirm the postgresql login is active, was entered without surrounding whitespace, and belongs to the intended PostgreSQL account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden PostgreSQL population as empty.
Wrong account or scope
Disconnect before retrying with the intended PostgreSQL identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the dedicated role retains CONNECT and schema USAGE for the affected catalog object.
  2. Check search_path-independent schema visibility, ownership, role inheritance, and row-security policy metadata access.
  3. Do not add table SELECT to solve a missing catalog object; correct the schema/catalog grants instead.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement postgresql login for the same PostgreSQL account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old postgresql login in PostgreSQL.