EDB PostgreSQL Professional case studies
EDB PostgreSQL Professional · Put your knowledge to work in context.
The EDB PostgreSQL Professional credential is positioned as a vendor-aligned certification for database professionals who administer, tune, protect, and migrate PostgreSQL estates, including deployments on EDB's commercial platform. It suits working DBAs, platform and infrastructure engineers, and migration or data-engineering specialists who already run PostgreSQL in production and want independent, structured validation of that experience. The EDB PostgreSQL Professional case studies are 5 cases and about 4,727 words.
1Anti-wraparound vacuum that never finishes
The primary has been up 412 days. Monitoring fires: age(datfrozenxid) for the orders database is 1.94 billion while autovacuum freeze max age is 200 million, and anti-wraparound workers have been cycling for nine days without finishing.
939 words, about 5 min2Estimator blow-up and planning-time tax on a partitioned table
An analytics API runs one query against events : 2.4 billion rows, range-partitioned by month into 36 partitions, with B-tree indexes on tenant id and created at plus a GIN index on a payload jsonb column. The query is issued from a prepared statement and the server switches to a generic plan after five executions.
921 words, about 5 min3Synchronous replication stall takes the primary down without a failure
Three-node cluster on EPAS 15: primary pg-a , standbys pg-b (same rack) and pg-c (other rack), streaming replication, managed by EDB Postgres Failover Manager with a floating VIP. The primary is configured with synchronous standby names = 'FIRST 2 (pg-b, pg-c)' , synchronous commit = on , wal sender timeout = 60s .
940 words, about 5 min4Oracle to EPAS cutover with a four-hour window
An Oracle 19c database of 1.6 TB must move to EDB Postgres Advanced Server 16. The source has 1,250 tables, 2,100 indexes, 214 PL/SQL packages, 380 synonyms, 22 database links, and heavy use of CONNECT BY , ROWNUM , NVL , DECODE , Oracle-style outer joins and PRAGMA AUTONOMOUS TRANSACTION .
937 words, about 5 min5PCI findings on an EPAS cluster under PEM management
A PCI review of an EPAS 16 cluster finds: 38 application nodes all connect as app super , a role with SUPERUSER that has no password expiry; pg hba.conf contains host all all 10.20.0.0/16 md5 ; password encryption is md5 ; no auditing is enabled in either EPAS's built-in edb audit facility or pgaudit ; and pg stat ssl reports zero TLS sessions. The cluster serves a 24×7 order service on 6 databases with 40 roles, and a connection pooler front-ends the application nodes.
990 words, about 5 min