Skip to main content
Community Hub

Advanced config for PostgreSQL

TL;DR

Reference for the PostgreSQL Advanced config credential settings - connection health check and server-side cursors - for servers that speak the PostgreSQL protocol but don't behave exactly like PostgreSQL.

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Advanced config sits under Database in the PostgreSQL credential form. It holds two compatibility settings for servers that speak the PostgreSQL protocol but don't behave exactly like PostgreSQL. Standard PostgreSQL, including Amazon RDS and Aurora, Azure Database for PostgreSQL, and Google Cloud SQL, works with the defaults.

Fields​

FieldDefaultWhat it doesChange it when
Advanced configDefaultShows the two settings below when set to Advanced. On Default they're hidden and ignored.You need either setting below.
Connection health checkEnabledChecks each pooled connection before reuse.Test Authentication fails with can't change 'autocommit' now: connection in transaction status INTRANS. Set to Disabled.
Server-side cursorsEnabledStreams query results in batches instead of loading them all at once.The crawl fails on DECLARE ... CURSOR with a syntax error, or the server rejects cursors. Set to Disabled.

At their defaults, the connection behaves like standard PostgreSQL.

warning

With Server-side cursors disabled, each extraction query loads its full result into memory. Only disable it when the server rejects cursors.

Field behavior​

  • The two settings only take effect when Advanced config is set to Advanced.
  • Switching Advanced config back to Default ignores both settings, whatever they were set to, so the connection uses the defaults.
  • Advanced config in the credential form is separate from the Advanced Config option in the crawler configuration step. Changing one doesn't affect the other.

See also​