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

Поиск
Список
Период
Сортировка
От Jahwan Kim
Тема Re: Cannot vacuum even in single-user mode after xidStopLimit is reached
Дата
Msg-id CADU5SwN4kgY3ukRQ9crQmoHTsNf1vhUGuGdnbka_JssP7vocUw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Cannot vacuum even in single-user mode after xidStopLimit isreached  (Arthur Zakirov <a.zakirov@postgrespro.ru>)
Список 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.zakirov@postgrespro.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

В списке pgsql-general по дате отправления:

Предыдущее
От: Arthur Zakirov
Дата:
Сообщение: Re: Cannot vacuum even in single-user mode after xidStopLimit isreached
Следующее
От: Ravi Krishna
Дата:
Сообщение: Re: WSL (windows subsystem on linux) users will need to turn fsyncoff as of 11.2