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. 424 Chapter 17 5432 | 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 path. • Fix pg_upgrade to handle event triggers in extensions correctly (Haribabu Kommi) pg_upgrade failed to preserve an event trigger’s extension-membership status. • Fix pg_upgrade’s cluster state

directory within that. This avoids permis- sions 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 of Network 5432 | 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 Notes • Fix pg_upgrade to handle event triggers in extensions correctly (Haribabu Kommi) pg_upgrade failed to preserve an event trigger’s extension-membership status. • Fix pg_upgrade’s cluster state

directory within that. This avoids permis- sions 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 of Network 5432 | 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 stdout would contain corrupt data due to failure to put the file descriptor into binary mode. • Fix pg_upgrade to ensure that the ending WAL record does not have wal_level = minimum (Bruce Momjian) This condition

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. 411 Chapter 17 your data. 425 Chapter 17. Server Setup and Operation 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 stdout would contain corrupt data due to failure to put the file descriptor into binary mode. • Fix pg_upgrade to ensure that the ending WAL record does not have wal_level = minimum (Bruce Momjian) This condition

...................................................................................2513 F.36. pg_upgrade .............................................................................................. Versions ................................................................................2514 F.36.2. pg_upgrade Options...............................................................................2514 F.36 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. 390 Chapter 17

...................................................................................2673 F.36. pg_upgrade .............................................................................................. ..................................................................................2674 F.36.2. pg_upgrade Options......................................................................................2674 directory within that. This avoids permis- sions 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 of Network

directory within that. This avoids permis- sions 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 of Network -p 5432 | psql -d postgres -p 5433 to transfer your data. 17.6.2. Upgrading Data via pg_upgrade The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL ver- sion requires steps similar to pg_dumpall above, e.g. starting/stopping the server, running initdb. The pg_upgrade documen- tation outlines the necessary steps. 17.6.3. Upgrading Data via Replication It is also

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. 446 Chapter 17 -p 5432 | psql -d postgres -p 5433 to transfer your data. 17.6.2. Upgrading Data via pg_upgrade The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version requires steps similar to pg_dumpall above, e.g. starting/stopping the server, running initdb. The pg_upgrade documentation outlines the necessary steps. 17.6.3. Upgrading Data via Replication It is also

..........................................................................................1973 pg_upgrade .............................................................................................. directory within that. This avoids permis- sions 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 of Network -p 5432 | psql -d postgres -p 5433 to transfer your data. 17.6.2. Upgrading Data via pg_upgrade The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL ver- sion

..........................................................................................1857 pg_upgrade .............................................................................................. 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. 468 Chapter 17 -p 5432 | psql -d postgres -p 5433 to transfer your data. 17.6.2. Upgrading Data via pg_upgrade The pg_upgrade module allows an installation to be migrated in-place from one major PostgreSQL version