| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: temporary file log lines |
| Date: | 2021-07-13 18:01:23 |
| Message-ID: | 64634f8c-1903-3328-291e-617a80096d02@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 7/13/21 9:29 AM, Guillaume Lelarge wrote:
> Hi,
>
> Le lun. 12 juil. 2021 à 14:13, MichaelDBA <MichaelDBA(at)sqlexec(dot)com
> <mailto:MichaelDBA(at)sqlexec(dot)com>> a écrit :
>
> hmmm, I think spilling over to disk for temporary tables is handled by
> an entirely different branch in the PG source code. In fact, some
> other
> folks have chimed in and said log_temp_files doesn't relate to temp
> files at all use by temporary tables, just queries as you mentioned
> below elsewhere. This seems to be a dark area of PG that is not
> convered well.
>
>
> As far as I know, log_temp_files only relates to sort/hash going to
> disks, not to temporary objects (tables and indexes).
>
Right. log_temp_files does not cover temporary tables.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tobias Gierke | 2021-07-16 21:27:24 | Linear slow-down while inserting into a table with an ON INSERT trigger ? |
| Previous Message | Guillaume Lelarge | 2021-07-13 07:29:33 | Re: temporary file log lines |