Re: Parallel query and temp_file_limit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel query and temp_file_limit
Date: 2016-06-21 03:01:50
Message-ID: 14317.1466478110@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Wed, May 18, 2016 at 3:40 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> What I'm tempted to do is trying to document that, as a point of
>> policy, parallel query in 9.6 uses up to (workers + 1) times the
>> resources that a single session might use. That includes not only CPU
>> but also things like work_mem and temp file space. This obviously
>> isn't ideal, but it's what could be done by the ship date.

> Where would that be documented, though? Would it need to be noted in
> the case of each such GUC?

Why can't we just note this in the number-of-workers GUCs? It's not like
there even *is* a GUC for many of our per-process resource consumption
behaviors.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-06-21 03:06:15 Re: primary_conninfo missing from pg_stat_wal_receiver
Previous Message Peter Eisentraut 2016-06-21 03:00:07 Re: primary_conninfo missing from pg_stat_wal_receiver