mirror of
https://github.com/postgres/postgres.git
synced 2025-11-21 00:42:43 +03:00
Rename "pg_clog" directory to "pg_xact".
Names containing the letters "log" sometimes confuse users into believing that only non-critical data is present. It is hoped this renaming will discourage ill-considered removals of transaction status data. Michael Paquier Discussion: http://postgr.es/m/CA+Tgmoa9xFQyjRZupbdEFuwUerFTvC6HjZq1ud6GYragGDFFgA@mail.gmail.com
This commit is contained in:
@@ -63,7 +63,7 @@ at about the same time would OR the same bits into the field, so there
|
||||
is little or no risk of conflicting update; what's more, if there did
|
||||
manage to be a conflict it would merely mean that one bit-update would
|
||||
be lost and need to be done again later. These four bits are only hints
|
||||
(they cache the results of transaction status lookups in pg_clog), so no
|
||||
(they cache the results of transaction status lookups in pg_xact), so no
|
||||
great harm is done if they get reset to zero by conflicting updates.
|
||||
Note, however, that a tuple is frozen by setting both HEAP_XMIN_INVALID
|
||||
and HEAP_XMIN_COMMITTED; this is a critical update and accordingly requires
|
||||
|
||||
Reference in New Issue
Block a user