pgsql: Update parallel BTree scan state when the scan keys can't be sat - Mailing list pgsql-committers

From Amit Kapila
Subject pgsql: Update parallel BTree scan state when the scan keys can't be sat
Date
Msg-id E1kIrX2-0004G2-8L@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Update parallel BTree scan state when the scan keys can't be satisfied.

For parallel btree scan to work for array of scan keys, it should reach
BTPARALLEL_DONE state once for every distinct combination of array keys.
This is required to ensure that the parallel workers don't try to seize
blocks at the same time for different scan keys. We missed to update this
state when we discovered that the scan keys can't be satisfied.

Author: James Hunter
Reviewed-by: Amit Kapila
Tested-by: Justin Pryzby
Backpatch-through: 10, where it was introduced
Discussion: https://postgr.es/m/4248CABC-25E3-4809-B4D0-128E1BAABC3C@amazon.com

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/0abd9cd2f3a1cad201ca28767aa0a720cc341179

Modified Files
--------------
src/backend/access/nbtree/nbtsearch.c | 4 ++++
1 file changed, 4 insertions(+)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Allow CURRENT_ROLE where CURRENT_USER is accepted
Next
From: Tom Lane
Date:
Subject: pgsql: Improve common/logging.c's support for multiple verbosity levels