This is interesting, although I'm not sure it's relevant. From pg_ctl source.
00477 write_stderr<http://doxygen.postgresql.org/bin_2psql_2common_8c.html#aeca3eef79cc2b37affc8d760c33e1de8> (_<http://doxygen.postgresql.org/elog_8c.html#af20b8d139279b360b0fdeae71f8f43bc> ("\n%s: -w option is not supported when starting a pre-9.1 server\n"), On Fri, Feb 15, 2013 at 9:45 AM, Ian Harding <harding....@gmail.com> 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 server > > > The funny thing is, the server starts instantly. > > > On Fri, Feb 15, 2013 at 9:19 AM, Jeff Janes <jeff.ja...@gmail.com> wrote: > >> On Fri, Feb 15, 2013 at 4:54 AM, Ian Harding <harding....@gmail.com> >> wrote: >> > 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. >> >> How long does the server take to start? >> >> If it takes the server more than 1 minute to start, then what you >> describe is expected. >> >> Cheers, >> >> Jeff >> > >
