Re: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp
Date: 2011-07-18 22:29:45
Message-ID: 4E24B3D9.7080702@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 19/07/11 02:36, Tom Lane wrote:
> Bruce Momjian<bruce(at)momjian(dot)us> writes:
>> Tom Lane wrote:
>>> Huh? Seems like a waste of text to me. What else would happen?
>> Well, if we exceed work_mem, we spill to temp disk. If we exceed temp
>> disk, we error out. Those different behaviors don't seem obvious to me.
> [ shrug... ] Feel free to change it.
>
>

No objections from me - can't see any harm in making it very clear what
happens when the limit is exceeded :-)

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2011-07-19 02:44:09 pgsql: Cascading replication feature for streaming log-based replicatio
Previous Message Tom Lane 2011-07-18 18:47:57 pgsql: Add GET STACKED DIAGNOSTICS plpgsql command to retrieve exceptio

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2011-07-18 22:29:51 Re: storing TZ along timestamps
Previous Message Joey Adams 2011-07-18 22:17:10 Re: Initial Review: JSON contrib modul was: Re: Another swing at JSON