aboutsummaryrefslogtreecommitdiff
path: root/src/backend/nodes/outfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-10-17 12:38:33 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-10-17 12:38:33 -0400
commit473320e6c87cc7ffc704b2823c685b3dd13c0342 (patch)
treee7d73803440d9c0c192813e53cc537705eb4a5f1 /src/backend/nodes/outfuncs.c
parentcacb65263b99c3d96aa4b250cdbda05072ade03e (diff)
downloadpostgresql-473320e6c87cc7ffc704b2823c685b3dd13c0342.tar.gz
postgresql-473320e6c87cc7ffc704b2823c685b3dd13c0342.zip
Close un-owned SMgrRelations at transaction end.
If an SMgrRelation is not "owned" by a relcache entry, don't allow it to live past transaction end. This design allows the same SMgrRelation to be used for blind writes of multiple blocks during a transaction, but ensures that we don't hold onto such an SMgrRelation indefinitely. Because an SMgrRelation typically corresponds to open file descriptors at the fd.c level, leaving it open when there's no corresponding relcache entry can mean that we prevent the kernel from reclaiming deleted disk space. (While CacheInvalidateSmgr messages usually fix that, there are cases where they're not issued, such as DROP DATABASE. We might want to add some more sinval messaging for that, but I'd be inclined to keep this type of logic anyway, since allowing VFDs to accumulate indefinitely for blind-written relations doesn't seem like a good idea.) This code replaces a previous attempt towards the same goal that proved to be unreliable. Back-patch to 9.1 where the previous patch was added.
Diffstat (limited to 'src/backend/nodes/outfuncs.c')
0 files changed, 0 insertions, 0 deletions