Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 2011-07-17T22:39:19Z
Lists: pgsql-hackers
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Tom Lane wrote: > >> Add temp_file_limit GUC parameter to constrain temporary file space usage. > >> > >> The limit is enforced against the total amount of temp file space used by > >> each session. > >> > >> Mark Kirkwood, reviewed by C?dric Villemain and Tatsuo Ishii > > > Should we document that sessions that exceed this limit generate an > > error? I don't see any mention of this in the docs. > > 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. The work_mem docs do mention is spills to disk though, so maybe it is OK. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add temp_file_limit GUC parameter to constrain temporary file space usage.
- 23e5b16c71f2 9.2.0 cited