A dump/restore using pg_dumpall   or use of pg_upgrade   or logical replication is required for those wishing to migrate data from any previous releas

PostgreSQL: Documentation: 16: E.1. Release 16

submited by
Style Pass
2023-05-25 14:00:11

A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 19.6 for general information on migrating to new major releases.

Version 16 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:

Previously, the string value of such variables was set to match the variable name during cursor assignment; now it will be assigned during OPEN, and will not match the variable name. To restore the previous behavior, assign the desired portal name to the cursor variable before OPEN.

Columns of parent/partitioned and child/partition tables must all have the same generation status, though now the actual generation expressions can be different.

The VACUUM/ANALYZE option is BUFFER_USAGE_LIMIT, and the vacuumdb option is --buffer-usage-limit. The default value is set by server variable vacuum_buffer_usage_limit, which also controls autovacuum.

Leave a Comment
Related Posts