shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results streaming replication feature (see Section 25.2.5). Servers will be either a Master or a Standby server. Masters can send data, while Standby(s) are always receivers of replicated data. When cascading replication

it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results streaming replication feature (see Section 25.2.5). Servers will be either a Master or a Standby server. Masters can send data, while Standby(s) are always receivers of replicated data. When cascading replication using replication it means that standby servers must be upgraded to 9.3.3 or later before their masters are. An older standby will be unable to interpret freeze records generated by a newer master, and

shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results streaming replication feature (see Section 25.2.5). Servers will be either a Master or a Standby server. Masters can send data, while Standby(s) are always receivers of replicated data. When cascading replication

it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results streaming replication feature (see Section 25.2.5). Servers will be either a Master or a Standby server. Masters can send data, while Standby(s) are always 478 Chapter 18. Server Configuration receivers of replicated this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the slave the master and shut down the older database instance. Such a switch-over results this error has been observed to result in significant “bloat” of standby servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results result in significant “bloat” of standby 1819 Appendix E. Release Notes servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode result in significant “bloat” of standby 1882 Appendix E. Release Notes servers compared to their masters, due to updates being applied far beyond where the end-of-file should have been. This failure mode

shm_use_phys. If running in FreeBSD jails by enabling sysctl’s security.jail.sysvipc_allowed, post- masters running in different jails should be run by different operating system users. This im- proves security it has synced up with the master server (running the older version of PostgreSQL), you can switch masters and make the standby the master and shut down the older database instance. Such a switch-over results streaming replication feature (see Section 25.2.5). Servers will be either a Master or a Standby server. Masters can send data, while Standby(s) are always receivers of replicated data. When cascading replication