Jon Nelson <jnelson+pgsql@xxxxxxxxxxx> writes: > On Sun, Feb 23, 2014 at 9:49 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> If memory serves, the inode should get removed during the next checkpoint. > I was moments away from commenting to say that I had traced the flow > of the code to md.c and found the comments there quite illuminating. I > wonder if there is a different way to solve the underlying issue > without relying on ftruncate (which seems to be somewhat expensive). Hm. The code is designed the way it is on the assumption that ftruncate doesn't do anything that unlink wouldn't have to do anyway. If it really is significantly slower on popular filesystems, maybe we need to revisit that. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
