Search Postgresql Archives

Cannot vacuum even in single-user mode after xidStopLimit is reached

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Any help or hint would be greatly appreciated.

Version 9.5.10
* PostgreSQL stopped, saying it needs vacuum.
* Checked the tables' age, and the top rows are as follows:
table_name                 |    age     | table_size 
--------------------------------------------+------------+------------
 pg_temp_31.tt_wms2_status    | 2146483647 | 0 bytes
 pg_temp_31.tt_wms2_string    | 2134022566 | 0 bytes
 pg_temp_16.tt_wms2_status    | 1464468964 | 0 bytes
 pg_temp_182.tt_wms2_status   | 1461637687 | 0 bytes
 pg_temp_182.tt_wms2_string   | 1453357513 | 0 bytes
 pg_temp_16.tt_wms2_string    | 1452951861 | 0 bytes
 pg_temp_4.tt_wms2_status     | 1452494376 | 0 bytes
...
( i.e., all are temp tables. )
* PostgreSQL hint says, "Stop the postmaster and vacuum"
* Tried to vacuum in single-user mode, only in vain, with something like drop that table, and "You might also need to commit or roll back old prepared transactions." also says xid will wrap around after 999998 transactions.
* Tried to drop table pg_temp_31.tt_wms2_status, tried to drop schema pg_temp_31. Nope. PostgreSQL hint says, "Stop the postmaster and vacuum"

So apparently I'm in some loop without any clear way out.
The most similar thing I found was "Could not finish anti-wraparound VACUUM when stop limit is reached" https://www.postgresql.org/message-id/53820ED9.3010003@xxxxxxxxxx. This is quite old, though.

Two questions:

(1) Can I revive this database?
(2) How did this possibly happen?

Best Regards,
Jahwan


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux