OSDN Git Service

When truncating a relation in-place (eg during VACUUM), do not try to unlink
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 20 Nov 2006 01:07:56 +0000 (01:07 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 20 Nov 2006 01:07:56 +0000 (01:07 +0000)
commit1a5c450f3024ac57cd6079186c71b3baf39e84eb
tree5c38669f870f990694459c09de39232fbbc4108b
parentd68efb3f8d868dc6bf4f86b8cdd5745b833b6dc4
When truncating a relation in-place (eg during VACUUM), do not try to unlink
any no-longer-needed segments; just truncate them to zero bytes and leave
the files in place for possible future re-use.  This avoids problems when
the segments are re-used due to relation growth shortly after truncation.
Before, the bgwriter, and possibly other backends, could still be holding
open file references to the old segment files, and would write dirty blocks
into those files where they'd disappear from the view of other processes.

Back-patch as far as 8.0.  I believe the 7.x branches are not vulnerable,
because they had no bgwriter, and "blind" writes by other backends would
always be done via freshly-opened file references.
src/backend/storage/smgr/md.c