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

From: Jahwan Kim <blgl13(dot)net(at)gmail(dot)com>
To: Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Cannot vacuum even in single-user mode after xidStopLimit is reached
Date: 2019-02-18 15:19:47
Message-ID: CADU5SwN4kgY3ukRQ9crQmoHTsNf1vhUGuGdnbka_JssP7vocUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <a(dot)zakirov(at)postgrespro(dot)ru>
wrote:

> 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 transaction either.
>
> Can you show the exact whole message?
>
> Do I understand correctly. Are temp tables persist in pg_class even
> after trying to drop temp tables in single-user mode?
>
> --
> Arthur Zakirov
> Postgres Professional: http://www.postgrespro.com
> Russian Postgres Company
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ravi Krishna 2019-02-18 15:33:50 Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2
Previous Message Arthur Zakirov 2019-02-18 15:11:49 Re: Cannot vacuum even in single-user mode after xidStopLimit is reached