database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-18 17:41:14 +03:00
Code

Correct comment in Hot Standby nbtree handling

Browse Source 
Logic is correct, matching handling of LP_DEAD elsewhere.
This commit is contained in:
Simon Riggs 2014-05-06 14:45:05 +01:00
parent a7a3e71c85
commit 41fdcf71d2
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/backend/access/nbtree/nbtxlog.c
View File

@ -719,11 +719,11 @@ btree_xlog_delete_get_latestRemovedXid(xl_btree_delete *xlrec)
UnlockReleaseBuffer(ibuffer); UnlockReleaseBuffer(ibuffer);
/* /*
* XXX If all heap tuples were LP_DEAD then we will be returning * If all heap tuples were LP_DEAD then we will be returning
* InvalidTransactionId here, causing conflict for all HS transactions. * InvalidTransactionId here, which avoids conflicts. This matches
* That should happen very rarely (reasoning please?). Also note that * existing logic which assumes that LP_DEAD tuples must already be
* caller can't tell the difference between this case and the fast path * older than the latestRemovedXid on the cleanup record that
* exit above. May need to change that in future. * set them as LP_DEAD, hence must already have generated a conflict.
*/ */
return latestRemovedXid; return latestRemovedXid;
} }