mirror of
https://github.com/postgres/postgres.git
synced 2025-07-30 11:03:19 +03:00
Fix obsolete FSM remarks in nbtree README.
The free space map has used a dedicated relation fork rather than shared memory segments for over a decade.
This commit is contained in:
@ -347,14 +347,11 @@ guaranteed to be "visible to everyone". As collateral damage, this
|
|||||||
implementation also waits for running XIDs with no snapshots and for
|
implementation also waits for running XIDs with no snapshots and for
|
||||||
snapshots taken until the next transaction to allocate an XID commits.
|
snapshots taken until the next transaction to allocate an XID commits.
|
||||||
|
|
||||||
Reclaiming a page doesn't actually change its state on disk --- we simply
|
Reclaiming a page doesn't actually change the state of the page --- we
|
||||||
record it in the shared-memory free space map, from which it will be
|
simply record it in the free space map, from which it will be handed out
|
||||||
handed out the next time a new page is needed for a page split. The
|
the next time a new page is needed for a page split. The deleted page's
|
||||||
deleted page's contents will be overwritten by the split operation.
|
contents will be overwritten by the split operation (it will become the
|
||||||
(Note: if we find a deleted page with an extremely old transaction
|
new right page).
|
||||||
number, it'd be worthwhile to re-mark it with FrozenTransactionId so that
|
|
||||||
a later xid wraparound can't cause us to think the page is unreclaimable.
|
|
||||||
But in more normal situations this would be a waste of a disk write.)
|
|
||||||
|
|
||||||
Because we never delete the rightmost page of any level (and in particular
|
Because we never delete the rightmost page of any level (and in particular
|
||||||
never delete the root), it's impossible for the height of the tree to
|
never delete the root), it's impossible for the height of the tree to
|
||||||
|
Reference in New Issue
Block a user