Re: fix for pg_upgrade - Mailing list pgsql-hackers

From panam
Subject Re: fix for pg_upgrade
Date
Msg-id 1317077650108-4843289.post@n5.nabble.com
Whole thread Raw
In response to Re: fix for pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
Responses Re: fix for pg_upgrade
List pgsql-hackers
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

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?

Thanks & regards,
panam

--
View this message in context: http://postgresql.1045698.n5.nabble.com/fix-for-pg-upgrade-tp3411128p4843289.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: bug of recovery?
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #6218: TRAP: FailedAssertion( "!(owner->nsnapshots == 0)", File: "resowner.c", Line: 365)