Maybe this is it. 8.4 pg_ctl docs say it uses "psql -l" to see if it's finished when you use -w. It also says
Default port for psql (used by the -w option).
And since pg_upgrade uses a funky port, it might miss unless the PGPORT environment variable is set to match.
I'll try that tonight.
On Fri, Feb 15, 2013 at 10:09 AM, Ian Harding <harding.ian@xxxxxxxxx> wrote:
This is interesting, although I'm not sure it's relevant. From pg_ctl source.On Fri, Feb 15, 2013 at 9:45 AM, Ian Harding <harding.ian@xxxxxxxxx> wrote:
-----------------------------------------------------------------
pg_upgrade run on Fri Feb 15 05:09:34 2013
-----------------------------------------------------------------command: "/usr/lib/postgresql/8.4/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/var/lib/postgresql/8.4/main/" -o "-p 50432 -c autovacuum=off -c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c unix_socket_permissions=0700" start >> "pg_upgrade_server.log" 2>&1
waiting for server to start...............................................................could not start serverThe funny thing is, the server starts instantly.On Fri, Feb 15, 2013 at 9:19 AM, Jeff Janes <jeff.janes@xxxxxxxxx> wrote:On Fri, Feb 15, 2013 at 4:54 AM, Ian Harding <harding.ian@xxxxxxxxx> wrote:How long does the server take to start?
> I don't think it would get any further... It fails and --retain says
> "Retain sql and log files after success" I can look at that log file and
> all it indicates is failure to start the server.
>
> Maybe I should rephrase the question: pg_ctl returns failure, even though
> it starts the server, when run with the -w flag.
If it takes the server more than 1 minute to start, then what you
describe is expected.
Cheers,
Jeff
