Takahiro Itagaki <itagaki.takah...@oss.ntt.co.jp> writes: > In mdunlink(), we truncate the first main fork to zero length > and actually unlink at the next checkpoint, but other segments > are not truncated and only unlinked. Then, if another backend > open the segments, disk spaces occupied by them are not reclaimed > until all of the backends close their file descriptors. Longer > checkpoint timeout and connection pooling make things worse.
Truncating seems like an ugly kluge that's not fixing the real problem. Why are there open descriptors for a dropped relation? They should all get closed as a consequence of relcache flush. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers