| From: | Ivan Voras <ivoras(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Feature request (or at least discussion): enable autovaccum on temp tables |
| Date: | 2019-05-31 15:39:51 |
| Message-ID: | CAF-QHFW-c9wCKGrsSWSG+Sf89_us7xfA+P_ci2_=qUbmzjTO+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 31 May 2019 at 17:34, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hi
>
> pá 31. 5. 2019 v 17:26 odesílatel Ivan Voras <ivoras(at)gmail(dot)com> napsal:
>
>> Hello,
>>
>>
>> autovacuum check tables once per minute, and working on closed
> transactions. Lot of times temporary tables are filled inside some batch,
> and immediately some query is started over this table. It is very low
> probability to analyze temp table at good time automatically. So only
> explicit call of ANALYZE is correct solution.
>
>
There are two types of workloads we're talking about: short ones, for which
autovacuum is probably not worth it, and long-running ones (in our case,
hours), where it is. So that's why I'm advocating a GUC toggle.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Brusselback | 2019-05-31 15:40:15 | Re: Feature request (or at least discussion): enable autovaccum on temp tables |
| Previous Message | Pavel Stehule | 2019-05-31 15:34:01 | Re: Feature request (or at least discussion): enable autovaccum on temp tables |