Re: pg_upgrade - Mailing list pgsql-general

From Ian Harding
Subject Re: pg_upgrade
Date
Msg-id CAMR4UwF+bfVb2yqLL95U_0sTYH8xehjihNJRwT6y=uFrDognmg@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade  (Ian Harding <harding.ian@gmail.com>)
Responses Re: pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general
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

PGPORT

Default port for
psql<http://www.postgresql.org/docs/8.4/static/app-psql.html>(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@gmail.com> wrote:

> 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.ian@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.janes@gmail.com> wrote:
>>
>>> On Fri, Feb 15, 2013 at 4:54 AM, Ian Harding <harding.ian@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
>>>
>>
>>
>

pgsql-general by date:

Previous
From: Joe Van Dyk
Date:
Subject: Re: Avoiding duplication of code via views -- slower? How do people typically do this?
Next
From: Tom Lane
Date:
Subject: Re: Avoiding duplication of code via views -- slower? How do people typically do this?