Magnus Hagander <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> So: maybe the solution is to add a step to the drop sequence, namely >> revoking any pending fsync request, before unlink.
> Perhaps we could have the bgwrite check the queue *if* it gets the > ENOENT/EACCESS error and then re-check the queue for drops on that file? I've committed a tentative patch along these lines to HEAD. Please test. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org