From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
---|---|
To: | Steve Purcell <steve(at)sanityinc(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 10:28:59 |
Message-ID: | 87skha85qs.fsf@hi-media-techno.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-07-06 11:26:38 | Re: Unknown winsock error 10061 |
Previous Message | wstrzalka | 2009-07-06 10:20:22 | Unknown winsock error 10061 |