diff options
| author | Noah Misch <noah@leadboat.com> | 2020-01-10 18:31:22 -0800 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2020-01-10 18:31:26 -0800 |
| commit | cb977424532f20fae65f2e58ac901286a2482b24 (patch) | |
| tree | 2205c796d4ecf46cc37d78150765b151b328a4a7 /src/backend/executor | |
| parent | 7b84ff33a14095b6252edbee686edf93ac9c8d1b (diff) | |
| download | postgresql-cb977424532f20fae65f2e58ac901286a2482b24.tar.gz postgresql-cb977424532f20fae65f2e58ac901286a2482b24.zip | |
Maintain valid md.c state when FileClose() fails.
FileClose() failure ordinarily causes a PANIC. Suppose the user
disables that PANIC via data_sync_retry=on. After mdclose() issued a
FileClose() that failed, calls into md.c raised SIGSEGV. This fix adds
repalloc() calls during mdclose(); update a comment about ignoring
repalloc() cost. The rate of relation segment count change is a minor
factor; more relevant to overall performance is the rate of mdclose()
and subsequent re-opening of segments. Back-patch to v10, where commit
45e191e3aa62d47a8bc1a33f784286b2051f45cb introduced the bug.
Reviewed by Kyotaro Horiguchi.
Discussion: https://postgr.es/m/20191222091930.GA1280238@rfd.leadboat.com
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions