Re: Feature request (or at least discussion): enable autovaccum ontemp tables

Поиск
Список
Период
Сортировка
От Ivan Voras
Тема Re: Feature request (or at least discussion): enable autovaccum ontemp tables
Дата
Msg-id CAF-QHFU+gakORnJ8KwysgYZMCBGvRoqUcxi8K_qhEFnkRZsUgA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Feature request (or at least discussion): enable autovaccum on temp tables  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Ответы Re: Feature request (or at least discussion): enable autovaccum ontemp tables  (Christopher Browne <cbbrowne@gmail.com>)
Re: Feature request (or at least discussion): enable autovaccum ontemp tables  (Michael Lewis <mlewis@entrata.com>)
Список pgsql-general
Дерево обсуждения
Hi,
On Fri, 31 May 2019 at 17:43, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:
>>>>> "Ivan" == Ivan Voras <ivoras@gmail.com> writes:

 Ivan> Since AFAIK temp tables are very close to unlogged ordinary
 Ivan> tables, what would stop this feature from being implemented?

The key difference between temp tables and other tables is that temp
table data does not use the shared_buffers but is buffered only in
backend-local memory.

This means that other processes (like, say, an autovacuum process) can
not access the content of temp tables. So what you want is not possible.

Understood.

So, a related question, since we have dozens of temp tables and a lot of code, is there a way to look up what temp tables are being created by the current session, so I can do a VACUUM or ANALYZE on all of them in bulk? I know I can inspect pg_temp_* schema, but how to figure out which one is from the current session?


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

Предыдущее
От: Ivan Voras
Дата:
Сообщение: Re: Feature request (or at least discussion): enable autovaccum ontemp tables
Следующее
От: Ron
Дата:
Сообщение: Re: Inherit Database - Table Permissions