15 docs tagged with "postgresql"

Integrate, catalog, and govern AlloyDB for PostgreSQL assets in Atlan.

Compare the three ways Atlan can reach your PostgreSQL database - internet with IP allowlisting, private connectivity, or a self-deployed agent - and pick the right one before touching any firewall.

Integrate, catalog, and govern Cloud SQL for PostgreSQL assets in Atlan.

The fastest path to connect Atlan to PostgreSQL - Atlan connects to your database's public endpoint over TLS, and you allowlist Atlan's fixed egress IPs. Five phases, each labeled with who performs it.

Configure and run PostgreSQL metadata extraction workflows to catalog databases, schemas, tables, views, and columns in Atlan.

The reference for gates 1 and 2 - what to allowlist where, how pg_hba.conf decides, and how to keep the SSL settings on both ends consistent. Applies to every connectivity method.

Enable pg_stat_statements and configure your PostgreSQL instance so the PostgreSQL Miner workflow can extract query history and generate lineage.

Understand how Atlan securely connects to your PostgreSQL database to extract metadata, with support for multiple authentication methods and deployment modes

A plain-language explanation of the journey a connection makes from Atlan to your PostgreSQL database - the three gates it must pass, the three paths it can take, and SSL in one minute.

Once you have [crawled assets from PostgreSQL](/apps/connectors/database/postgresql/how-tos/crawl-postgresql), you can mine its query history to construct lineage.

Integrate, catalog, and govern PostgreSQL assets in Atlan

Private connectivity from Atlan to Azure Database for PostgreSQL is a support-assisted VNet peering setup - what to ask for, what you configure yourself, and the caveats to insist on before signing off.

Private connectivity to PostgreSQL on Google Cloud depends on what the database is - Cloud SQL and AlloyDB have Private Service Connect paths under their own connectors; self-managed Postgres uses the self-deployed agent.

On-premises PostgreSQL, many databases behind one PrivateLink, Aurora failovers and moving IPs, Azure and GCP hosting, cross-region IAM authentication, and VPC Lattice.

Symptom-first troubleshooting for PostgreSQL connectivity - SSL and pg_hba rejections, timeouts, IAM authentication, wrong PrivateLink hostname, misleading error wrappers, and miner preflight failures.