Re: WIP - Add ability to constrain backend temporary file space - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIP - Add ability to constrain backend temporary file space
Date
Msg-id 16365.1298065283@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIP - Add ability to constrain backend temporary file space  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-hackers
Mark Kirkwood <mark.kirkwood@catalyst.net.nz> writes:
> Added. With respect to the datatype, using int with KB units means the 
> largest temp size is approx 2047GB - I know that seems like a lot now... 
> but maybe someone out there wants (say) their temp files limited to 
> 4096GB :-)

[ shrug... ]  Sorry, I can't imagine a use case for this parameter where
the value isn't a *lot* less than that.  Maybe if it were global, but
not if it's per-backend.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: WIP - Add ability to constrain backend temporary file space
Next
From: Bruce Momjian
Date:
Subject: Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues)