> ------- Original Message -------
> From: Tom Lane <[EMAIL PROTECTED]>
> To: "Dorochevsky,Michel" <[EMAIL PROTECTED]>
> Sent: 23/04/07, 19:51:51
> Subject: Re: [BUGS] BUG #3245: PANIC: failed to re-find shared loc k o b j ect
>
> "Dorochevsky,Michel" <[EMAIL PROTECTED]> writes:
> > I am not used to the command line tools. So I made a backup
> > using the pgadmin GUI. I selected options 'PLAIN format', 'with OIDs' and
> > 'schema only'. See
> > www.dorochevsky.de/infos/TestSchema.txt
> > I hope that is what you needed.
>
> Yeah, this is great, particularly since it includes the OIDs. However,
> the OIDs don't seem to entirely match up with the LOCK_DEBUG output.
> I'm wondering if somehow we're locking the wrong OIDs? Hard to believe
> a bug like that could've escaped detection though. Still trying to
> trace through it to see where things first go wrong. (If anyone else is
> looking at this, note that a constraint's index will generally have an
> OID one less than the constraint, so you can infer the OIDs of indexes
> that aren't explicitly given in the dump.)
For Michel's benefit; pgAdmin 1.6.3 and below incorrectly display the index OID
for unique/pkey constraints, not the constraint OID. Hope this doesn't confuse!
The next version will correct the bug and display the index OID as well for
good measure.
/D
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
