On Wed, May 28, 2014 at 11:28:47PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Wed, May 28, 2014 at 04:56:53PM -0700, Adrian Klaver wrote:
> >> So for my edification, does that mean -O ' -c
> >> config_file=/etc/postgresql/9.3/main/postgresql.conf' could cause a
> >> problem or that starting Postgres outside pg_upgrade could cause a
> >> problem, or both.
>
> > Starting Postgres outside pg_upgrade would _certainly_ cause a problem.
>
> It appeared to me that it was failing safely, ie, once somebody had
> started a conflicting postmaster, pg_upgrade's attempt to start one
> failed without damage.
Yes, it was. The thing we can't block is an administrator starting the
old or new postmaster while pg_upgrade isn't using it, then shutting it
down before pg_upgrade needs it --- seems unlikely though.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
