Skip site navigation (1) Skip section navigation (2)

Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore

From: Steve Purcell <steve(at)sanityinc(dot)com>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Date: 2009-07-06 13:11:19
Message-ID: E264DA28-0CE4-46C6-91D0-FE556E60DD70@sanityinc.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Terrific, thanks for that. I'd figured out the first trick you  
suggested, but the second is much clearer.

-Steve



On 6 Jul 2009, at 12:28, Dimitri Fontaine wrote:

> Steve Purcell <steve(at)sanityinc(dot)com> writes:
>
>> # su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
>> PGCLUSTER=8.4/main pg_restore -d template1 -C"
>>
>> And the debian pg_wrapper script ends up selecting the 8.3 pg_dump  
>> binary in
>> the first case.  I'll have to figure out if there's even a  way to  
>> execute
>> the newer pg_dump against the old database, which I  expect to be
>> fiddly.
>
> I guess you could trick the binary choice then force another server
> choice :
> pg_dump --cluster 8.4/main -p <port of 8.3> ...
>
> But I'd simply go with:
> /usr/lib/postgresql/8.4/bin/pg_dump <options to target 8.3>
>
> For people unaware of debian way of supporting more than one major
> version and cluster, all PostgreSQL user binaries in /usr/bin are a  
> link
> to their pg_wrapper, which support the --cluster 8.X/clustername  
> option
> and will choose the right versionned binary and port number etc.
>
> Regards,
> -- 
> dim
>


In response to

pgsql-bugs by date

Next:From: Gerhard LeykamDate: 2009-07-06 13:41:11
Subject: Re: BUG #4897: PostgreSQL 8.3.7 crashes on Win2003 logoff
Previous:From: Dave PageDate: 2009-07-06 12:22:41
Subject: Re: Unknown winsock error 10061

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group