Re: pg_upgrade

From: Ian Lawrence Barwick <barwick(at)gmail(dot)com>
To: Ian Harding <harding(dot)ian(at)gmail(dot)com>
Cc: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade
Date: 2013-02-15 06:41:50
Message-ID: CAB8KJ=iut-eV7A+3AdReJfYW_G1QLec3_JMXw_sDSJxv24EQ_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013/2/15 Ian Harding <harding(dot)ian(at)gmail(dot)com>
>
>
> On Feb 14, 2013, at 9:50 PM, Ian Lawrence Barwick <barwick(at)gmail(dot)com> wrote:
>
> 2013/2/15 Ian Harding <harding(dot)ian(at)gmail(dot)com>
>>
>> When I run pg_upgrade, it tries to start the old cluster with the -w flag, which waits a while and declares failure, even though it starts the server. If I start/stop without -w everything is great.
>>
>> Can I tell pg_upgrade not to use that flag, or is there a reason it is not working that I should look into?
>>
>> version
>> ------------------------------------------------------------------------------------------------------
>> PostgreSQL 8.4.8 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.4.real (Debian 4.4.5-8) 4.4.5, 64-bit
>>
>
> Which PostgreSQL version is the old cluster, and which version is the new cluster? What options are you supplying to pg_upgrade, and what output are you getting?
>

> Old is 8.4, new is 9.2. I am not supplying an but the minimum options and --check succeeds. My
> pg_ctl fails when run by hand with -w (although the database does start) so I know that's the issue.

Maybe try running pg_upgrade with the --retain option and check
pg_upgrade_server.log for clues?

Ian Barwick

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joe Van Dyk 2013-02-15 07:00:26 Re: Avoiding duplication of code via views -- slower? How do people typically do this?
Previous Message Ian Harding 2013-02-15 05:59:25 Re: pg_upgrade