select_parallel test fails with nonstandard block size

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: select_parallel test fails with nonstandard block size
Date: 2016-09-15 12:26:35
Message-ID: 90634e20-097a-e4fd-67d5-fb2c42f0dd71@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

When building with --with-blocksize=16, the select_parallel test fails
with this difference:

explain (costs off)
select sum(parallel_restricted(unique1)) from tenk1
group by(parallel_restricted(unique1));
- QUERY PLAN
-----------------------------------------------------
+ QUERY PLAN
+-------------------------------------------
HashAggregate
Group Key: parallel_restricted(unique1)
- -> Index Only Scan using tenk1_unique1 on tenk1
-(3 rows)
+ -> Gather
+ Workers Planned: 4
+ -> Parallel Seq Scan on tenk1
+(5 rows)

set force_parallel_mode=1;
explain (costs off)

We know that different block sizes cause some test failures, mainly
because of row ordering differences. But this looked a bit different.

The size of the tenk1 table is very similar under either block size:

16k: tenk1 = 2883584
8k: tenk1 = 2932736

Is there an explanation for this difference, or is there something wrong
in the cost estimation somewhere?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2016-09-15 12:29:51 Re: sequences and pg_upgrade
Previous Message Heikki Linnakangas 2016-09-15 11:57:13 Re: OpenSSL 1.1 breaks configure and more