Re: gp_dump: error in finding the last system oid: ERROR: get_relation_info: Relation 1262 not found

tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote in message news:<7673(dot)1044166693(at)sss(dot)pgh(dot)pa(dot)us>...
> charette(at)writeme(dot)com (Stephane Charette) writes:
> > dumping database "log"...
> > pg_dump: error in finding the last system oid: ERROR:
> > get_relation_info: Relation 1262 not found
>
> Don't tell me you did something as foolish as dropping pg_database?
> No? Well, maybe you've got a corrupted index. Try running a reindex on
> pg_class, or on all the system catalogs if that doesn't help. See the
> REINDEX reference page for details on the arcane procedure to follow.

No, I did not drop pg_database. I followed the steps to start a
standalone backend in the reference guide under "REINDEX", but it
doesn't seem to be working. This is what I tried:

$ /usr/local/pgsql/bin/postgres -D /usr/local/stuff/data -O -P log
DEBUG: database system was shut down at 2003-01-31 22:10:57 GMT
DEBUG: checkpoint record is at 0/1AF664

DEBUG: redo record is at 0/1AF664; undo record is at 0/0; shutdown
TRUE
DEBUG: next transaction id: 196; next oid: 16632
DEBUG: database system is ready

POSTGRES backend interactive interface
$Revision: 1.245.2.3 $ $Date: 2002/09/30 20:47:22 $

backend> reindex database log force
NOTICE: relation 1247 was reindexed
NOTICE: relation 1249 was reindexed
ERROR: Cannot create unique index. Table contains non-unique values
backend>

What does this mean, and how do I fix it?

Stephane Charette
stephanecharette <nospam> AT telus <nospam> .net