From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Ivan Voras <ivoras(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL Mailing Lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Feature request (or at least discussion): enable autovaccum on temp tables |
Date: | 2019-05-31 16:33:59 |
Message-ID: | CAFNqd5Up76ZHiO=XvhwEDBXYNVeaNQZygBcvXgw=zmuegjGmhg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 31, 2019, 12:26 PM Ivan Voras <ivoras(at)gmail(dot)com> wrote:
> Hi,
> On Fri, 31 May 2019 at 17:43, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
> wrote:
>
>> >>>>> "Ivan" == Ivan Voras <ivoras(at)gmail(dot)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?
>
I think you might want to look at information_schema.tables; I seem to
recall that view restricting itself to the tables actually visible to your
connection.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2019-05-31 17:00:57 | Re: Feature request (or at least discussion): enable autovaccum on temp tables |
Previous Message | Ron | 2019-05-31 16:26:31 | Re: Inherit Database - Table Permissions |