Search Postgresql Archives

Re: Database corruption with duplicate tables.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



George Woodring <george.woodring@xxxxxxxxxx> writes:
> Upon investigation I found that I have a table that is in the database twice

> db=> select oid, relname from pg_class where oid IN (26770910,
> 26770918, 26770919);
>    oid    |                relname
> ----------+---------------------------------------
>  26770910 | availcpedata_20100410
>  26770918 | availcpedata_20100410_date_index
>  26770919 | availcpedata_20100410_pollgrpid_index
>  26770910 | availcpedata_20100410
> (4 rows)

It's not immediately clear whether that's really two instances of the
row for availcpedata_20100410, or a false hit due to index corruption.
If you include ctid in the query, do the rows have distinct ctids?
If not, reindexing pg_class should fix it.

> Can anyone suggest a strategy for removing the table?  I don't want to
> start randomly deleting stuff from the catalogs.

If there are two, manually deleting one is the only way to fix it.  Use
the ctid to make sure you remove only one ...

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux