mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix out-of-date version reference, grammar.

Browse Source 
Time appears to be passing fast.

Reported-By: Peter Geoghegan <pg@bowt.ie>
This commit is contained in:
Andres Freund 2020-08-12 17:04:51 -07:00
parent dc7420c2c9
commit b8443eae72
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/access/nbtree/README
View File

@ -412,7 +412,7 @@ the cost of walking down the tree in such common cases.
The optimization works on the assumption that there can only be one
non-ignorable leaf rightmost page, and so not even a visible-to-everyone
style interlock required. We cannot fail to detect that our hint was
style interlock is required. We cannot fail to detect that our hint was
invalidated, because there can only be one such page in the B-Tree at
any time. It's possible that the page will be deleted and recycled
without a backend's cached page also being detected as invalidated, but

2
src/backend/access/transam/README
View File

@ -318,7 +318,7 @@ XID less than this could be about to appear in the ProcArray, because of the
XidGenLock interlock discussed above.)
As GetSnapshotData is performance critical, it does not perform an accurate
oldest-xmin calculation (it used to, until v13). The contents of a snapshot
oldest-xmin calculation (it used to, until v14). The contents of a snapshot
only depend on the xids of other backends, not their xmin. As backend's xmin
changes much more often than its xid, having GetSnapshotData look at xmins
can lead to a lot of unnecessary cacheline ping-pong. Instead