Re: fix for pg_upgrade

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: fix for pg_upgrade
Дата
Msg-id 201109270000.p8R00Xn03290@momjian.us
обсуждение исходный текст
Ответ на Re: fix for pg_upgrade  (panam <panam@gmx.net>)
Ответы Re: fix for pg_upgrade
Список pgsql-hackers
panam wrote:
> Hi Bruce,
> 
> on the old DB I've got 465783 as oid whereas on the new one it is 16505.
> 
> is not in the dump file (old db), even 16385 (i guess this is a typo here)
> or 16505 are not.
> The only line in which 465783 could be found is

I need to see the lines after this.

> Is that enough information or should I send the whole dump? That's a bit of
> work as I have to expunge some sensitive schema data, or is there a
> meaningful way to just do the dump for a single db?

You can do:
pg_dump --binary-upgrade --schema-only dbname


--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [BUGS] BUG #6218: TRAP: FailedAssertion( "!(owner->nsnapshots == 0)", File: "resowner.c", Line: 365)
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [BUGS] BUG #6218: TRAP: FailedAssertion( "!(owner->nsnapshots == 0)", File: "resowner.c", Line: 365)