RE: [ADMIN] SOS !!: Porstgress forgot all ! Help !

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Jean-Arthur Silve'" <jeanarthur(at)eurovox(dot)fr>
Cc: "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: [ADMIN] SOS !!: Porstgress forgot all ! Help !
Date: 2001-02-12 17:28:03
Message-ID: 8F4C99C66D04D4118F580090272A7A234D32E7@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Then if I reindex my DB I have :
>
> NOTICE: --Relation astro--
> NOTICE: Pages 204: Changed 0, reaped 0, Empty 0, New 0; Tup
> 4878: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 324, MaxLen 324;
> Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. CPU
0.04s/0.18u sec.
> NOTICE: Index astro_pkey: Pages 25; Tuples 4878. CPU 0.01s/0.01u sec.
>
> If I do :
> select * from astro;
>
> I have :
>
...
> (0 rows)

Well, it may be caused by corrupted next_xid in pg_variable.
Could you

CREATE TABLE foo (bar int);
select xmin from pg_class where relname = 'foo';

and say what is exact size of pg_log file?

Vadim

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-02-12 17:36:30 Re: PL/PgSQL GET DIAGNOSTICS command
Previous Message Peter Eisentraut 2001-02-12 16:43:26 Re: PL/PgSQL GET DIAGNOSTICS command