Re: WIP - Add ability to constrain backend temporary file space

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP - Add ability to constrain backend temporary file space
Date: 2011-02-18 22:40:59
Message-ID: 4D5EF57B.7020106@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19/02/11 11:30, Josh Berkus wrote:
>> Yeah, the disadvantage is that (like statement timeout) it is a 'bottom
>> of the cliff' type of protection. The advantage is there are no false
>> positives...
> Yeah, just trying to get a handle on the proposed feature. I have no
> objections; it seems like a harmless limit for most people, and useful
> to a few.
>
No worries and sorry, I should have used the "per backend" phrase in the
title to help clarify what was intended.

Cheers

Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-02-18 22:47:42 disposition of remaining patches
Previous Message Josh Berkus 2011-02-18 22:30:13 Re: WIP - Add ability to constrain backend temporary file space