diff options
| author | Andres Freund <andres@anarazel.de> | 2016-09-08 16:51:09 -0700 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2016-09-08 16:52:13 -0700 |
| commit | 26ce63ce76f91eac7570fcb893321ed0233d62ff (patch) | |
| tree | 00722c5290bce1e4a31ac82f262c2affeaca0403 /src/backend/access/gist | |
| parent | 142a110b312fa2d6bbc4eba4df196c35e0caf7bb (diff) | |
| download | postgresql-26ce63ce76f91eac7570fcb893321ed0233d62ff.tar.gz postgresql-26ce63ce76f91eac7570fcb893321ed0233d62ff.zip | |
Fix mdtruncate() to close fd.c handle of deleted segments.
mdtruncate() forgot to FileClose() a segment's mdfd_vfd, when deleting
it. That lead to a fd.c handle to a truncated file being kept open until
backend exit.
The issue appears to have been introduced way back in 1a5c450f3024ac5,
before that the handle was closed inside FileUnlink().
The impact of this bug is limited - only VACUUM and ON COMMIT TRUNCATE
for temporary tables, truncate files in place (i.e. TRUNCATE itself is
not affected), and the relation has to be bigger than 1GB. The
consequences of a leaked fd.c handle aren't severe either.
Discussion: <20160908220748.oqh37ukwqqncbl3n@alap3.anarazel.de>
Backpatch: all supported releases
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions