Re: select_parallel test fails with nonstandard block size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: select_parallel test fails with nonstandard block size
Date: 2016-09-15 15:05:45
Message-ID: 10511.1473951945@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, Sep 15, 2016 at 10:44 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, sure, but at any reasonable value of min_parallel_relation_size
>> that won't be a factor. The question here is whether we want the default
>> value to be platform-independent. I notice that both config.sgml and
>> postgresql.conf.sample claim that the default value is 8MB, which this
>> discussion reveals to be a lie. If you want to keep the default expressed
>> as "1024" and not "(8 * 1024 * 1024) / BLCKSZ", we need to change the
>> documentation.

> I don't particularly care about that. Changing it to 8MB always would
> be fine with me.

OK, I'll take care of it (since I now realize that the inconsistency
is my own fault --- I committed that GUC not you). It's unclear what
this will do for Peter's complaint though.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-15 15:10:28 Re: Surprising behaviour of \set AUTOCOMMIT ON
Previous Message Tom Lane 2016-09-15 15:03:23 Re: Printing bitmap objects in the debugger