Karl DeBisschop wrote:
> I came in this morning to find my network monitor reporting a problem
> with one of our databases.
>
> The error was:
>
> FATAL 1: Index pg_class_relname_index is not a btree
>
> I was able to access all the other databases, so I dumped them each
> (pg_dumpall conects first to template1, so that was not an option).
>
> Then I shut down and restarted the database. It came back up clean. But
> when I tried to do pg_dumpall on that, there were no tables present.
> Sure enough, a select on pg_database revealed only one -- template1.
>
> I can connect to the other database:
>
> template1=> select * from pg_database;
> datname | datdba | encoding | datpath
> -----------+--------+----------+-----------
> template1 | 10002 | 0 | template1
> (1 row)
>
> template1=> \connect biobase
> You are now connected to database biobase.
> biobase=>
>
> But I can't do anything.
>
> I should also note that the data directory is a symlink - the OS was
> updraded over the weekend onto a new disk. The database directory itself
> was then mounted from the old disk. Not sure this is relevant though -
> the DB was fine for more than 48 hours after the switchover.
>
> This is RedHat Linux 6.2 with the PostgreSQL 7.0.2-2 RPM. If the
> hardware is relevant, it is a dual processor (Intel Xeon) machine -- the
> OS now lives on an IDE drive, while the data is on a SCSI drive. Prior
> to Saturday, the OS and data both lived on the SCSI drive, and the OS
> was RedHat 6.0 -- the database has been 7.0.2 for some time now, that
> was not upgraded over the weekend (although the bits were freshened, the
> version is exactly the same).
>
> Has anyone seen this before? Any ideas?
>
> --
> Karl DeBisschop kdebisschop@alert.infoplease.com
> Family Education Network/Information Please http://www.infoplease.com
> Netsaint Plugin Developer kdebisschop@users.sourceforge.net
This reminds me of something : are there any plans to include roll forward
support on postgreSQL ?
Jurgen
