Re: [PATCH] Re: [BUGS] BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve - Mailing list pgsql-hackers

From Pavel Raiskup
Subject Re: [PATCH] Re: [BUGS] BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve
Date
Msg-id 2173089.HqHtjyoHSD@nb.usersys.redhat.com
Whole thread Raw
In response to Re: [PATCH] Re: [BUGS] BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [PATCH] Re: [BUGS] BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
> The patch moves the atexit setting up, as you suggested, but only does
> that when pg_ctl succeeds (we know we started the server),

Yes, of course!

> PG 9.1+ will allow pg_ctl -w start to succeed even if there are
> permissions problems;  earlier versions will not and will keep the
> server running --- the user will have to stop the server after
> pg_upgrade says it is running.

This makes it a complex, really..  We may not easily make the
stop_postmaster resistant to non-running server.  Thus your solution must
be good enough.

> I am not going to backpatch this beyond 9.3 as it is risky code.  I have
> improved the comments in this area.

Agree, it is OK for me — thanks for your work.

Pavel




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCH] Re: [BUGS] BUG #7815: Upgrading PostgreSQL from 9.1 to 9.2 with pg_upgrade/postgreql-setup fails - invalid status retrieve
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #8335: trim() un-document behaviour