Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
От | Dimitri Fontaine |
---|---|
Тема | Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore |
Дата | |
Msg-id | 87skha85qs.fsf@hi-media-techno.com обсуждение исходный текст |
Ответ на | Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore (Steve Purcell <steve@sanityinc.com>) |
Ответы |
Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
|
Список | pgsql-bugs |
Steve Purcell <steve@sanityinc.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
В списке pgsql-bugs по дате отправления: