Re: Query running for very long time (server hanged) with parallel append - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Query running for very long time (server hanged) with parallel append
Date
Msg-id CA+TgmoYqdC+9U8mLYkUgM=CaBt6Pzz4R_YNboqDbW-LvUaHO+g@mail.gmail.com
Whole thread Raw
In response to Re: Query running for very long time (server hanged) with parallel append  (Amit Khandekar <amitdkhan.pg@gmail.com>)
Responses Re: Query running for very long time (server hanged) with parallelappend  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
On Tue, Feb 6, 2018 at 11:32 AM, Amit Khandekar <amitdkhan.pg@gmail.com> wrote:
> Yeah, I think it looks equally good that way, and like you said, the
> current code does it that way. So in the attached patch, I have
> swapped the two conditions.

I prefer to avoid introducing 2 new variables and instead just prevent
the looping directly in the case where we started with a non-partial
plan.

See attached.  Does this look OK?

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

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Next
From: Peter Eisentraut
Date:
Subject: Re: Add more information_schema columns