pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Holger Jakobs <holger@jakobs.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: small temp files
Date: Mon, 22 Jul 2024 07:28:45 -0600
Message-ID: <8E03B792-C389-456D-913D-4F2B0EBB903E@elevated-dev.com> (raw)
In-Reply-To: <a9dee6e8-6197-d9bb-028e-6d020167bf57@jakobs.com>
References: <7A0C9A69-5632-4CFC-B156-53FAAAB33E26@elevated-dev.com>
	<a9dee6e8-6197-d9bb-028e-6d020167bf57@jakobs.com>

> On Jul 22, 2024, at 7:00 AM, Holger Jakobs <holger@jakobs.com> wrote:
> 
> Typically, queries which need a lot of memory (RAM) create temp files if work_mem isn't sufficient for some sorting or hash algorithms.
> 
> Increasing work_mem will help, but small temp files don't create any trouble.
> 
> You can set work_mem within each session, don't set it high globally.

I understand those things--my question is why, with work_mem set to 128MB, I would see tiny temp files (7452 is common, as is 102, and I've seen as small as 51).






view thread (8+ messages)  latest in thread

Message-ID: <8E03B792-C389-456D-913D-4F2B0EBB903E@elevated-dev.com>
Permalink:  ../8E03B792-C389-456D-913D-4F2B0EBB903E@elevated-dev.com/
Also on:    postgresql.org/message-id/8E03B792-C389-456D-913D-4F2B0EBB903E@elevated-dev.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: scott_ribe@elevated-dev.com, holger@jakobs.com, pgsql-admin@lists.postgresql.org
  Subject: Re: small temp files
  In-Reply-To: <8E03B792-C389-456D-913D-4F2B0EBB903E@elevated-dev.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox