diff options
author | Andres Freund <andres@anarazel.de> | 2016-05-04 01:54:20 -0700 |
---|---|---|
committer | Andres Freund <andres@anarazel.de> | 2016-05-04 01:54:20 -0700 |
commit | a712487087c73eee880ff1a7c50528cbab2f1b90 (patch) | |
tree | 4d423e318a056ced0de24e6643619a8519c8adc4 /src/backend/utils/adt/numeric.c | |
parent | 613fb29a384c8a75146af7cfa433cfa61716f117 (diff) | |
download | postgresql-a712487087c73eee880ff1a7c50528cbab2f1b90.tar.gz postgresql-a712487087c73eee880ff1a7c50528cbab2f1b90.zip |
Fix transient mdsync() errors of truncated relations due to 72a98a6395.
Unfortunately the segment size checks from 72a98a6395 had the negative
side-effect of breaking a corner case in mdsync(): When processing a
fsync request for a truncated away segment mdsync() could fail with
"could not fsync file" (if previous segment < RELSEG_SIZE) because
_mdfd_getseg() now wouldn't return the relevant segment anymore.
The cleanest fix seems to be to allow the caller of _mdfd_getseg() to
specify whether checks for RELSEG_SIZE are performed. To allow doing so,
change the ExtensionBehavior enum into a bitmask. Besides allowing for
the addition of EXTENSION_DONT_CHECK_SIZE, this makes for a nicer
implementation of EXTENSION_REALLY_RETURN_NULL.
Besides mdsync() the only callsite that should change behaviour due to
this is mdprefetch() which now doesn't create segments anymore, even in
recovery. Given the uses of mdprefetch() that seems better.
Reported-By: Thom Brown
Discussion: CAA-aLv72QazLvPdKZYpVn4a_Eh+i4_cxuB03k+iCuZM_xjc+6Q@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions