[GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Silvela, Jaime \(Exchange\)
I’ve seen that some other people have had ERROR could not open relation with OID ###   The suggested cause was somebody trying to drop a table in the middle of   VACUUM.   In my case, the error seems to be spreading. Initially it affected only one table in a staging area that would get

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Tom Lane
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > WARNING: terminating connection because of crash of another server > process This is not an interesting message: the interesting message is the previous one about exactly what happened to the other process. Look earlier in the server lo

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Silvela, Jaime \(Exchange\)
aime -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 5:20 PM To: Silvela, Jaime (Exchange) Cc: pgsql-general Subject: Re: [GENERAL] CASCADING could not open relation with OID "Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Tom Lane
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > If I try to read from one, I get ERROR: could not open relation with > OID 16896 > If I try to redefine it, I get ERROR: relation "bb_master" already > exists > If I try to DROP it, ERROR: cache lookup failed for relation 16896 What do

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Silvela, Jaime \(Exchange\)
) Cc: pgsql-general Subject: Re: [GENERAL] CASCADING could not open relation with OID "Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > If I try to read from one, I get ERROR: could not open relation with > OID 16896 > If I try to redefine it, I get ERROR: rel

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Tom Lane
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > I get values frin the first statement but not from the second. What values exactly ... particularly the OID? > After setting indexscan to off, still the same thing. > Should this setting be off in general? Certainly not! That was just

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Silvela, Jaime \(Exchange\)
: pgsql-general Subject: Re: [GENERAL] CASCADING could not open relation with OID "Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > I get values frin the first statement but not from the second. What values exactly ... particularly the OID? > After setting indexscan

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Tom Lane
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > I get > Oid: 16896 > Relname: bb_master Hmm ... but you're *sure* "where oid = 16896" can't find this row, even with enable_indexscan = off? That doesn't make a lot of sense. To cut to the chase, though: try "REINDEX pg_class" and see i

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Silvela, Jaime \(Exchange\)
EMAIL PROTECTED] Sent: Wednesday, August 23, 2006 7:10 PM To: Silvela, Jaime (Exchange) Cc: pgsql-general Subject: Re: [GENERAL] CASCADING could not open relation with OID "Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > I get > Oid: 16896 > Relname: bb_master Hm

Re: [GENERAL] CASCADING could not open relation with OID

2006-08-23 Thread Tom Lane
"Silvela, Jaime \(Exchange\)" <[EMAIL PROTECTED]> writes: > What could be the possible cause for this? Hard to say ... have you had any hardware flakiness lately? Are you running an up-to-date PG release? regards, tom lane ---(end of broadcast)---