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 the reply.
> >
> > (1) The pr
On 18.02.2019 17:18, Jahwan Kim wrote:
Thanks for the reply.
(1) The problem is, I cannot drop any of the temp tables, not even in
the single-user mode. It says
'vacuum', 'You might also need to commit or roll back old prepared
transactions.'
And, no, there seems to be no pending prepared tra
Thanks for the reply.
(1) The problem is, I cannot drop any of the temp tables, not even in the
single-user mode. It says
'vacuum', 'You might also need to commit or roll back old prepared
transactions.'
And, no, there seems to be no pending prepared transaction either.
Best,
Jahwan
On Mon, Feb
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-wraparound
VACUUM when stop limit is reached"
https://www.postgresql.org/message-id/53820ed9.3010...@vmware.com. This
is quite old,
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
