Re: Parallel query and temp_file_limit - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Parallel query and temp_file_limit
Date
Msg-id 14317.1466478110@sss.pgh.pa.us
Whole thread Raw
In response to Re: Parallel query and temp_file_limit  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Parallel query and temp_file_limit  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Peter Geoghegan <pg@heroku.com> writes:
> On Wed, May 18, 2016 at 3:40 AM, Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: primary_conninfo missing from pg_stat_wal_receiver
Next
From: Tom Lane
Date:
Subject: Re: primary_conninfo missing from pg_stat_wal_receiver