pgsql: Do no reset bounded before incremental sort rescan

From: Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Do no reset bounded before incremental sort rescan
Date: 2020-05-09 17:42:03
Message-ID: E1jXTUB-0001VN-KI@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Do no reset bounded before incremental sort rescan

ExecReScanIncrementalSort was resetting bounded=false, which means the
optimization would be disabled on all rescans. This happens because
ExecSetTupleBound is called before the rescan, not after it.

Author: James Coleman
Reviewed-by: Tomas Vondra
Discussion: https://postgr.es/m/20200414065336.GI1492@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/9155b4be9a13038d59a7a09a27b7fbce3819eb08

Modified Files
--------------
src/backend/executor/nodeIncrementalSort.c | 1 -
1 file changed, 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-05-09 20:28:31 pgsql: Fix findoidjoins to recognize oidvector columns.
Previous Message Tom Lane 2020-05-09 17:05:15 pgsql: Update oidjoins regression test for v13.