References ..... 2411 F.31.6. Authors ..... 2411 F.32. pg_upgrade ..... 2411 F.32.1. Supported Versions ..... 2411 F.32.2. pg_upgrade Options ..... 2412 F.32.3. Upgrade Steps ..... 2413 F.32 installation like this will not work.) ##### 24.4.2. Other data migration methods The contrib program pg_upgrade allows an installation to be migrated in-place from one major PostgreSQL version to the next. Keep that this method does not provide any scope for running old and new versions concurrently. Also, pg_upgrade is much less battle-tested than pg_dump, so having an up-to-date backup is strongly recommended

E.26.3.10. Source Code ..... 2214 E.26.3.11. Additional Modules ..... 2216 E.26.3.11.1. pg_upgrade ..... 2216 E.26.3.11.2. pgbench ..... 2216 E.26.3.12. Documentation ..... 2217 E.27 data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use | psql -d postgres -p 5433 to transfer your data. ##### 17.6.2. Non-Dump Upgrade Methods The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version to the

pg_archivecleanup ..... 2864 pg_standby ..... 2867 pg_test_fsync ..... 2871 pg_test_timing ..... 2873 pg_upgrade ..... 2877 H. External Projects ..... 2884 H.1. Client Interfaces ..... 2884 H.2. Administration data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use | psql -d postgres -p 5433 to transfer your data. ##### 17.6.2. Non-Dump Upgrade Methods The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version to the

pg_archivecleanup ..... 2693 pg_standby ..... 2696 pg_test_fsync ..... 2700 pg_test_timing ..... 2702 pg_upgrade ..... 2706 H. External Projects ..... 2712 H.1. Client Interfaces ..... 2712 H.2. Administration data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use | psql -d postgres -p 5433 to transfer your data. ##### 17.6.2. Non-Dump Upgrade Methods The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version to the

data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use | psql -d postgres -p 5433 to transfer your data. ##### 17.6.2. Non-Dump Upgrade Methods The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version to the consistency with a behavior recently added to pg_ctl; it eases automated testing on slow machines. - Fix pg_upgrade to correctly restore extension membership for operator families containing only one operator class

Cluster ..... 460 17.6.1. Upgrading Data via pg_dumpall ..... 460 17.6.2. Upgrading Data via pg_upgrade ..... 462 17.6.3. Upgrading Data via Replication.....462 17.7. Preventing Server Spoofing... pg_archivecleanup ..... 2329 pg_standby ..... 2332 pg_test_fsync ..... 2336 pg_test_timing ..... 2338 pg_upgrade ..... 2342 pg_xlogdump ..... 2349 H. External Projects ..... 2351 H.1. Client Interfaces data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use

Cluster .....487 17.6.1. Upgrading Data via pg_dumpall .....488 17.6.2. Upgrading Data via pg_upgrade .....490 17.6.3. Upgrading Data via Replication .....490 17.7. Preventing Server Spoofing 2475 pg_standby ..... 2478 pg_test_fsync ..... 2482 pg_test_timing ..... 2484 pg_upgrade ..... 2488 pg_xlogdump ..... 2495 H. External Projects ..... 2497 H.1. Client Interfaces data directory within that. This avoids permissions problems, particularly for operations such as pg_upgrade, and it also ensures clean failures if the secondary volume is taken offline. ##### 17.2.2. Use

installation and upgrade instructions. - The pg_upgrade_jobs parameter enables the --jobs flag in pg_upgrade that enables parallel upgrade checks, as well as parallel schema dump and restore, and parallel returns when it encounters an error during a write operation. ## Upgrade 184 Disables the command pg_upgrade --check on the primary segments so it only runs on the Greenplum master, which results in faster Improves the performance for restoring the target cluster schema with pg_upgrade. Adds a new pg_upgrade check to look for duplicated distribution columns that may be present in the database due to a

Cluster ..... 482 17.6.1. Upgrading Data via pg_dumpall ..... 483 17.6.2. Upgrading Data via pg_upgrade ..... 484 17.6.3. Upgrading Data via Replication ..... 484 17.7. Preventing Server Spoofing pg_resetxlog ..... 1850 pg_rewind ..... 1852 pg_test_fsync ..... 1855 pg_test_timing ..... 1857 pg_upgrade ..... 1861 pg_xlogdump ..... 1868 postgres ..... 1870 postmaster ..... 1878 VII. Internals Commands ..... 2284 E.26.3.9.2. pg_dump ..... 2285 E.26.3.9.3. pg_ctl ..... 2285 E.26.3.9.4. pg_upgrade ..... 2285 E.26.3.9.5. pgbench ..... 2286 E.26.3.10. Source Code ..... 2286 E.26.3.10.1.

References ..... 2261 F.31.6. Authors ..... 2261 F.32. pg_upgrade ..... 2261 F.32.1. Supported Versions ..... 2262 F.32.2. pg_upgrade Options ..... 2262 F.32.3. Upgrade Steps ..... 2263 F.32 installation like this will not work.) ##### 24.4.2. Other data migration methods The contrib program pg_upgrade allows an installation to be migrated in-place from one major PostgreSQL version to the next. Keep that this method does not provide any scope for running old and new versions concurrently. Also, pg_upgrade is much less battle-tested than pg_dump, so having an up-to-date backup is strongly recommended