Horton

Re: Fix for parallel BTree initialization bug

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@bowt.ie>, Justin Pryzby <pryzby@telsasoft.com>, "Jameson, Hunter 'James'" <hunjmes@amazon.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Robert Haas <rhaas@postgresql.org>, Rahila Syed <rahila.syed@2ndquadrant.com>
Date: 2020-09-17T12:51:59Z
Lists: pgsql-hackers 
On Tue, Sep 15, 2020 at 8:54 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Amit Kapila <amit.kapila16@gmail.com> writes:
> > On Mon, Sep 14, 2020 at 11:26 PM Peter Geoghegan <pg@bowt.ie> wrote:
> >> The fix seems sensible to me.
>
> > Thanks, I think it is better to wait for a day or two as yesterday
> > only we stamped 13 and we need to backpatch this.
>
> Right, please avoid pushing anything non-critical to REL_13_STABLE
> until you see the git tag appear.  I doubt we will need to re-wrap
> the tarballs, but you never know.
>

Pushed now. Sorry Peter, I forgot to give you reviewer credit in the
commit message but I really appreciate your nod for this patch.

-- 
With Regards,
Amit Kapila.

Commits

  1. Update parallel BTree scan state when the scan keys can't be satisfied.

  2. btree: Support parallel index scans.