- 1 What's New in PostgreSQL 9.6
- 1.1 Parallel Query
- 1.2 postgres_fdw
- 1.3 Synchronous Replication
- 1.4 Transactions, VACUUM and the Visibility Map
- 1.5 Other Features
- 1.5.1 Extension cascade support to install dependencies
- 1.5.2 Cube extension kNN support
- 1.5.3 Command progress reporting
- 1.5.4 Detailed wait information in pg_stat_activity
- 1.5.5 Index-only scans for partial indexes
- 1.5.6 Performance improvements for external sort operations
- 1.5.7 Phrase full text search
- 1.5.8 New API for hot physical backups
What's New in PostgreSQL 9.6
This page is a work in progress which will include details of PostgreSQL 9.6 features and changes. Many thanks to Thom Brown for assembling the original list.
Parallel sequential scans
DML (UPDATE/DELETE) pushdown
New remote_apply replication mode which waits for confirmation that a standby has applied changes
Support for multiple synchronous standbys
Transactions, VACUUM and the Visibility Map
pg_visibility extension for examining visibility maps
Frozen page data in visibility map for skipping vacuum on already-frozen data
User-defined expiration of snapshots to control table bloat
Until now a long-running report or cursor displaying query results could block cleanup of dead rows, bloating all volatile tables in the database. The only options were to allow the bloat, suspend normal updates to other tables, or kill the long-running activity -- which might be completely unrelated to the bloating tables. Accumulation of bloat could cause performance problems and excessive use of storage space.
A new configuration option called old_snapshot_threshold allows the cluster to be configured to allow cleanup of a dead row when the transaction which updated or deleted it (causing it to be dead) has completed and all snapshots which can still see it have reached a certain age, without immediately terminating activities which are using such snapshots. If, for example, a large monthly report is running off of data in table etl_monthly (which is not currently changing), bloat in other tables will be limited, and the report can run to completion without error. If a snapshot has passed the threshold and a query uses that snapshot to attempt to read data from a page modified recently enough that it might not produce accurate results, then a "snapshot too old" error will be thrown. Normally the goal in configuring old_snapshot_threshold is to set it high enough that such an error is rarely seen, while preventing problems caused by bloat.
Extension cascade support to install dependencies
Cube extension kNN support
Command progress reporting
Detailed wait information in pg_stat_activity
Index-only scans for partial indexes
Performance improvements for external sort operations
Phrase full text search
New API for hot physical backups
Prior to PostgreSQL 9.6, the only way to perform concurrent physical backups was through pg_basebackup, via the streaming replication protocol. Low-level file system copy was only available in an exclusive mode, by calling pg_start_backup(), initiating the copy of data files, then finally calling pg_stop_backup().
The limitation of taking one backup at a time has been overcome by a new native API which redefines the pg_start_backup() method and adds a variant to pg_stop_backup(). For back-compatibility, the older signatures have been kept.
The new pg_start_backup function now accepts a third optional parameter, called 'exclusive', which is set by default to 'true' for backward compatibility. Initiating a concurrent (or if you prefer, a non-exclusive) backup is rather simple:
SELECT pg_start_backup('my_label', false, false);
If you are not familiar with pg_start_backup(), the first argument is a label for the backup, while the second is a request for a fast checkpoint operation. The third parameter, when set to false, requests a concurrent backup:
postgres=# SELECT pg_start_backup('my_label', true, false); -[ RECORD 1 ]---+---------- pg_start_backup | 0/F000028
The PostgreSQL connection requesting the concurrent backup needs to remain active for the whole duration of the physical copy of data files (performed with your favourite tools such as rsync, cp, tar, SAN or LVM snapshots, ...). Note: this operation follows the same procedure as with prior versions of PostgreSQL (for detailed information, please refer to the documentation about continuous archiving and Point-In-Time-Recovery).
When finished, we need to use the new version of pg_stop_backup() to specify that we are closing the current non-exclusive backup:
SELECT * FROM pg_stop_backup(false);
The different signature has a mandatory parameter, called 'exclusive', which needs to be set to 'false' for concurrent backup. The reason is that the function returns a different result, a row made up of three fields:
- LSN, for backup consistency, returned at pg_stop_backup() time: identical to the previous version
- the content of the label file: this needs to be saved as 'backup_label' in the main backup directory (new in 9.6)
- the list of tablespaces: if not empty, this needs to be saved as 'tablespace_map' in the main backup directory (new in 9.6)
postgres=# SELECT * FROM pg_stop_backup(false); NOTICE: pg_stop_backup complete, all required WAL segments have been archived -[ RECORD 1 ]------------------------------------------------------------- lsn | 0/F000130 labelfile | START WAL LOCATION: 0/F000028 (file 00000001000000000000000F)+ | CHECKPOINT LOCATION: 0/F000060 + | BACKUP METHOD: streamed + | BACKUP FROM: master + | START TIME: 2016-05-16 09:19:44 CEST + | LABEL: my_label + | spcmapfile | 16386 /Users/gabriele/pg96/tbs1 + | 16388 /Users/gabriele/pg96/tbs2 + |
As you can see, these two steps require users to change their customised backup scripts. However, users should expect common disaster recovery and backup external solutions such as Barman, OmniPITR, PgBackRest, pghoard, WAL-E to transparently manage this new behaviour introduced in 9.6.
This new in-core API replaces the pgespresso package that was previously used with Barman 1.3.1 and above. Barman 2.0 now supports both pgespresso for PG9.2-PG9.5 and the new 9.6 API.
IMPORTANT: this new API will become the only supported way in the future to coordinate low level backup operations with PostgreSQL.