diff options
| author | Noah Misch <noah@leadboat.com> | 2016-01-01 01:46:46 -0500 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2016-01-01 01:46:46 -0500 |
| commit | 3cd1ba147e5619199914e5b71e0edbd188a763d2 (patch) | |
| tree | d432c0bc1e148464da6114325c623573baa8ae0b /src/backend/access/gist/gistproc.c | |
| parent | 253de19b8414b8b91e0fd710c2b492dc6375f9fa (diff) | |
| download | postgresql-3cd1ba147e5619199914e5b71e0edbd188a763d2.tar.gz | |
Fix comments about WAL rule "write xlog before data" versus pg_multixact.
Recovery does not achieve its goal of zeroing all pg_multixact entries
whose accompanying WAL records never reached disk. Remove that claim
and justify its expendability. Detail the need for TrimMultiXact(),
which has little in common with the TrimCLOG() rationale. Merge two
tightly-related comments. Stop presenting pg_multixact as specific to
heap_lock_tuple(); PostgreSQL 9.3 extended its use to heap_update().
Noticed while investigating a report from Andres Freund.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions