Re: Corrupt indices on already-dropped table (could not open relation with OID ...)

From: Craig de Stigter <craig(dot)destigter(at)koordinates(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Corrupt indices on already-dropped table (could not open relation with OID ...)
Date: 2009-11-17 20:18:05
Message-ID: e260aad40911171218p777b7a07rfd8b975662ef3732@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> What PG version is this exactly? Do you have any idea how you got into
> this state?
>

Using PostgreSQL 8.3.7-0ubuntu8.10.1 from the Intrepid repository.
version() is PostgreSQL 8.3.7 on i486-pc-linux-gnu, compiled by GCC
gcc-4.3.real (Ubuntu 4.3.2-1ubuntu11) 4.3.2

No database crashes or system restarts were involved. We accidentally had
two transactions open which were writing new rows to the table and then
creating the same indices. One failed with a 'could not open relation with
OID X' error and the other continued but failed for some unrelated reason.
When we dropped the table and tried to recreate the table we noticed the
indices were still there.

I don't see a reason to beterribly concerned about the consistency of the
> entries about this index.

The only issue is that we do want to be able to create that table again...

Thanks a bunch
Craig de Stigter
--
Koordinates Ltd
PO Box 1604, Shortland St, Auckland, New Zealand
Phone +64-9-966 0433 Fax +64-9-969 0045
Web http://www.koordinates.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kurt 2009-11-17 20:31:09 cast record to array in plpgsql
Previous Message Richard Huxton 2009-11-17 20:13:46 Re: does encrypt function support higher than basic ascii?