Why Postgres Professional
500+
DBMS developers and technical specialists
3000+ customers
including largest government and business structures
30+ years
of PostgreSQL development
TOP-3
largest PostgreSQL contributors
24x7
expert customer support with 1-hour SLA
100+ patches
are contributed to Postgres by our team annually
Postgres Pro Key Advantages
Feature Comparison
Key featuresEnhancements developed by Postgres Professional team |
Postgres Pro
|
Postgres Pro
|
|---|---|---|
| Failover configuration: a primary server plus standby servers | ||
| Data compression | ||
| 64-bit transaction ID (xid) | ||
| Block-level incremental backup with data consistency checks | ||
| Built-in task scheduler | ||
| Efficient partitioning for 10,000+ partitions | ||
| Corrupted WAL data recovery feature | ||
| Transparent Data Encryption | ||
| Full list of features | Request a Demo | Start a free trial |
News
PostgreSQL 19: part 5.4 (SQL, DEV1 and DEV2) of CommitFest 2026-03
We’re wrapping up our review of the March CommitFest for PostgreSQL 19. This fourth and final article in the series covers the changes related to SQL and to our DEV1 and DEV2 courses.
As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:
Part 5.4 (SQL, DEV1, DEV2) -- you are here 🙂
For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.
Here’s what’s covered:
- INSERT … ON CONFLICT DO SELECT
- COPY FROM: replacing invalid values with NULL
- COPY TO: exporting data in JSON format
- jsonpath: new string methods
- IS JSON predicate with domain types
- postgres_fdw: remote transactions inherit READ ONLY and DEFERRABLE modes
- Integrity constraints: altering the enforceability of CHECK constraints
- Integrity constraints: changing the generation expression of virtual columns with CHECK constraints
- Casting between uuid and bytea, and base32hex format support
- PL/pgSQL: SELECT … INTO optimization
- tid_block and tid_offset functions
- TOAST: lz4 as the default compression method
...
PostgreSQL 19: part 5.3 (DBA3 and DBS) of CommitFest 2026-03
We’re continuing our review of the March CommitFest for PostgreSQL 19. This third article in the series covers the changes related to our DBA3 and DBS courses.
As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:
Part 5.3 (DBA3, DBS) -- you are here 🙂
Part 5.4 (SQL, DEV1, DEV2)
For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.
Here’s what’s covered:
- pg_verifybackup, pg_waldump: reading WAL from tar archives
- pg_stat_recovery: monitoring replication and recovery
- psql: replica indicator in the prompt
- pg_createsubscriber --logdir: writing diagnostics to files
- Publications: excluding specific tables
- Logical replication subscriptions: connecting via postgres_fdw
- wal_sender_shutdown_timeout: limiting the wait for WAL replication at shutdown
- wal_receiver_timeout: per-user and per-subscription settings
- SSL: server-side SNI
- GRANT/REVOKE … GRANTED BY
- Password expiration warning
- MD5 passwords: more end-of-support preparations
- pg_[read|write]_all_data: now for large objects too
- psql: comments for publications, subscriptions, and extended statistics
...
PostgreSQL 19: part 5.2 (DBA1 and DBA2) of CommitFest 2026-03
We’re continuing our review of the March CommitFest for PostgreSQL 19. This second article in the series covers the changes related to our DBA1 and DBA2 courses.
As a reminder, here’s the plan for our coverage of the final PostgreSQL 19 CommitFest:
Part 5.2 (DBA1, DBA2) -- you are here 🙂
Part 5.3 (DBA3, DBS)
Part 5.4 (SQL, DEV1, DEV2)
For the earlier CommitFests, see: 2025-07, 2025-09, 2025-11, 2026-01.
Here’s what’s covered:
- REPACK: rewriting a table to reclaim disk space
- Autovacuum: table processing order
- Autovacuum: parallel index vacuuming
- Enhanced transaction ID wraparound warnings
- Checkpoint reason in the completion log message
- Less WAL and on-access visibility map updates
- More code paths use read streams
- pg_stat_lock: statistics on long lock waits
- pg_upgrade: faster large object transfer, part 2
- oid2name: file paths relative to PGDATA
- psql: comments on internal queries
- log_min_messages per backend type
- Stats reset time for pg_stat_database_conflicts and pg_statio_all_sequences
...
Customers