Re: ddd

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, tcook(at)blackducksoftware(dot)com, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Subject: Re: ddd
Date: 2017-12-21 15:35:06
Message-ID: CA+Tgmoa=pcD7yRCjv7OS=7kb4OyKFRk6aGB1GpNZuoVmC8aqbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 21, 2017 at 10:18 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> If I run the regression tests with force_parallel_mode=on prior to the
> parallel hash join patch, they pass. If I run them now, they fail
> inside the parallel hash join tests here:
>
> create table wide as select generate_series(1, 2) as id, rpad('',
> 320000, 'x') as t;
>
> I'm guessing that test case would have failed before, too, but we
> didn't have it. I'll analyze this further in a bit.

I think this is just a poorly-written assertion. currentCommandIdUsed
is only used to skip redundant increments of the command counter, and
CommandCounterIncrement() is categorically denied under parallelism
anyway. Therefore, it's OK for this to happen in parallel mode; we
just need to be in the leader, not the worker.

Therefore, I proposed the attached patch, which fixes the regression
test crash for me.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
cci-fix.patch application/octet-stream 848 bytes

In response to

  • Re: ddd at 2017-12-21 15:18:05 from Robert Haas

Responses

  • Re: ddd at 2017-12-21 17:55:24 from Andres Freund

Browse pgsql-hackers by date

  From Date Subject
Next Message Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= 2017-12-21 15:35:14 Re: !<space>= should give error?
Previous Message Tom Lane 2017-12-21 15:34:31 Re: force parallel mode vs CTAS