diff options
| author | Andres Freund <andres@anarazel.de> | 2015-12-14 11:34:16 +0100 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2015-12-14 11:34:16 +0100 |
| commit | cca705a5d93446e1a9c775b94c7d5900986c0488 (patch) | |
| tree | 5c724ee9ef2d1080ed5eef98bc7e926607c0b50a /src/backend/parser/parse_utilcmd.c | |
| parent | 2a3544960eaa114d34e5e83ab19e180c8efcd299 (diff) | |
| download | postgresql-cca705a5d93446e1a9c775b94c7d5900986c0488.tar.gz postgresql-cca705a5d93446e1a9c775b94c7d5900986c0488.zip | |
Fix bug in SetOffsetVacuumLimit() triggered by find_multixact_start() failure.
Previously, if find_multixact_start() failed, SetOffsetVacuumLimit() would
install 0 into MultiXactState->offsetStopLimit if it previously succeeded.
Luckily, there are no known cases where find_multixact_start() will return
an error in 9.5 and above. But if it were to happen, for example due to
filesystem permission issues, it'd be somewhat bad: GetNewMultiXactId()
could continue allocating mxids even if close to a wraparound, or it could
erroneously stop allocating mxids, even if no wraparound is looming. The
wrong value would be corrected the next time SetOffsetVacuumLimit() is
called, or by a restart.
Reported-By: Noah Misch, although this is not his preferred fix
Discussion: 20151210140450.GA22278@alap3.anarazel.de
Backpatch: 9.5, where the bug was introduced as part of 4f627f
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions