Tom Lane wrote:
I think the same, but I'm at the end of my ideas...Kamil Srot <kamil.srot@xxxxxxxxx> writes:# select xmin, age(xmin) from pg_class; xmin | age -----------+------------ 2 | 2147483647 2 | 2147483647 2 | 2147483647 2 | 2147483647 2 | 2147483647 2 | 2147483647 236838019 | 539453 2 | 2147483647 2 | 2147483647 231899309 | 5478163 etc.I see no indication here that there's anything wrong at all. The rows with xmin = 2 (ie, FrozenTransactionID) are evidently pg_class rows that have never been modified since the database was created. There isn't anything wrong with them. age() is returning INT_MAX for them to denote that they are "infinitely far in the past", but they are in no danger of being invalidated by wraparound. It's completelly gone... cannot do anything with this relation... I fixed it by creating this specific table from several hours old backup and it's fine (this table is nearly static)...You haven't yet showed us any details of what happens. What exactly do you mean by the table "disappearing"? Can you select from it? Do you see a row for it in pg_class? I didn't check if the relation was in pg_class... but I have complete backup of database files after this issue from today and also from the last time it happened (but they was vacuumed few hour before the backup by nightly script, so the data can be changed in this snapshots)... but it it can help and you'll navigate me, I can fetch any data you want from it... Thank you, -- Kamil |