RE: [ADMIN] SOS !!: Porstgress forgot all ! Help ! - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: [ADMIN] SOS !!: Porstgress forgot all ! Help !
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D32E7@sectorbase1.sectorbase.com
Whole thread Raw
List 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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: PL/PgSQL GET DIAGNOSTICS command
Next
From: Bruce Momjian
Date:
Subject: Re: PL/PgSQL GET DIAGNOSTICS command