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

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_te

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

Jahwan On Mon, Feb 18, 2019 at 10:49 PM Arthur Zakirov wrote: > Hello, > > On 18.02.2019 15:05, Jahwan Kim wrote: > > So apparently I'm in some loop without any clear way out. > > The most similar thing I found was "Could not finish anti-wraparou

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

Sorry I don't have the exact message right now, but YES. To be exact, drop table | schema pg_temp_XX... in single-user mode results in "HINT: run vaccum" On Tue, Feb 19, 2019 at 12:11 AM Arthur Zakirov wrote: > On 18.02.2019 17:18, Jahwan Kim wrote: > > Thanks for th

PostgreSQL temp table blues

Hi all, I'd like to share my (painful) experience, in which temp tables caused PostgreSQL shutdown. TL;DR. Do not use temp tables in PostgreSQL with connection pool. * My app uses connection pool AND temp tables, with default setting of ON COMMIT PRESERVE ROWS. * I found out later that autovacuu