database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-12 16:21:30 +03:00
Code

Fix misleading comment in nodeIndexonlyscan.c.

Browse Source 
The stated reason for acquiring predicate locks on heap pages hasn't
existed since commit c01262a8, so fix the comment.  Perhaps in a later
release we'll also be able to change the code to use tuple locks.

Back-patch all the way.

Reviewed-by: Ashwin Agrawal
Discussion: https://postgr.es/m/CAEepm%3D2GK3FVdnt5V3d%2Bh9njWipCv_fNL%3DwjxyUhzsF%3D0PcbNg%40mail.gmail.com
This commit is contained in:
Thomas Munro 2019-06-28 11:11:26 +12:00
parent 30e1b395c9
commit 0908c5ecf0
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/executor/nodeIndexonlyscan.c
View File

@ -179,11 +179,8 @@ IndexOnlyNext(IndexOnlyScanState *node)
errmsg("lossy distance functions are not supported in index-only scans"))); errmsg("lossy distance functions are not supported in index-only scans")));
/* /*
* Predicate locks for index-only scans must be acquired at the page * If we didn't access the heap, then we'll need to take a predicate
* level when the heap is not accessed, since tuple-level predicate * lock explicitly, as if we had. For now we do that at page level.
* locks need the tuple's xmin value. If we had to visit the tuple
* anyway, then we already have the tuple-level lock and can skip the
* page lock.
*/ */
if (tuple == NULL) if (tuple == NULL)
PredicateLockPage(scandesc->heapRelation, PredicateLockPage(scandesc->heapRelation,