From f763b77193b04eba03a1f4ce46df34dc0348419e Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 3 Sep 2012 13:52:34 -0400 Subject: Fix pg_upgrade to cope with non-default unix_socket_directory scenarios. When starting either an old or new postmaster, force it to place its Unix socket in the current directory. This makes it even harder for accidental connections to occur during pg_upgrade, and also works around some scenarios where the default socket location isn't usable. (For example, if the default location is something other than "/tmp", it might not exist during "make check".) When checking an already-running old postmaster, find out its actual socket directory location from postmaster.pid, if possible. This dodges problems with an old postmaster having a configured location different from the default built into pg_upgrade's libpq. We can't find that out if the old postmaster is pre-9.1, so also document how to cope with such scenarios manually. In support of this, centralize handling of the connection-related command line options passed to pg_upgrade's subsidiary programs, such as pg_dump. This should make future changes easier. Bruce Momjian and Tom Lane --- doc/src/sgml/pgupgrade.sgml | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index b62aba26418..9e43f3ce133 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -519,6 +519,14 @@ psql --username postgres --file script.sql postgres -d /real-data-directory -o '-D /configuration-directory'. + + If doing + A Log-Shipping Standby Server () cannot be upgraded because the server must allow writes. The simplest way -- cgit v1.2.3