> > O, your system reached max transaction ID -:(
>
> That's two reports now of people who have managed to wrap around the XID
> counter. It doesn't seem that hard to do in a heavily used database.
>
> Does anyone want to take more seriously the stopgap solution I proposed
> for this proble
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
>> before this manipulmation, pg_log = 1.073.741.824
> O, your system reached max transaction ID -:(
That's two reports now of people who have managed to wrap around the XID
counter. It doesn't seem that hard to do in a heavily used database.
Do
> before this manipulmation, pg_log = 1.073.741.824
O, your system reached max transaction ID -:(
> and xmin = 4982339
And now all tuples with xmin > ~500 are invisible.
One way to restore data could be hack vacuum to update
xmin of all valid tuples to 512, vacuum all tables,
dump dat
> 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:
