Preflight checks for PostgreSQL
Run preflight checks before the PostgreSQL crawler to validate connectivity, permissions, and configuration - and decode failures that happen before any check runs.
Before running the PostgreSQL crawler, you can run preflight checks to perform the necessary technical validations. The following preflight check will be completed:
Database and schema check
✅ Check successful
❌ Check failed for $missingObjectName
Tables check
✅ Check successful. Table count: <count>
❌ Check failed. Missing some of the required grants SELECT, SHOW VIEW, EXECUTE on tables:
S3
✅ Check successful if the bucket, region, and prefix combination is valid and the S3 credential passed is accessible.
❌Check failed with error code <AWS error code> - <AWS SDK ERR message>
For example: Miner S3 credentials: failed with error code: NoSuchBucket
When preflight fails before any check runs
Preflight can also fail at the connection level - before the checks above execute. These failures often surface as generic wrappers (SQL client authentication failed / ATLAN-CLIENT-401-02, Not able to authenticate your credentials, HEKA-500-00-009) whose wording is misleading: the word "authentication" in the wrapper is not evidence of an authentication problem. Expand the workflow logs and find the innermost error line:
| Innermost error contains | Real cause | Fix |
|---|---|---|
connection timeout expired | Firewall, wrong hostname, stale IP, or unopened port - not credentials | Timeouts |
pg_hba.conf rejects connection ... SSL off (often with PAM authentication failed) | Server requires SSL; connection sent none | SSL rejections |
permission denied for table ... | Missing grants - not connectivity | Set up PostgreSQL |
| No inner error at all | Possibly Atlan-side | Misleading wrappers |