"Tom Lane" <[EMAIL PROTECTED]> wrote
>
> The cleanest solution seems to be to make the bgwriter create and use a
> ResourceOwner, and probably get rid of the special hack in resowner.c
> that allows CurrentResourceOwner to be NULL.
>
Is that true that every moment the bgwriter just has one buffer
I think that bug #2099
http://archives.postgresql.org/pgsql-bugs/2005-12/msg00075.php
is probably explained by the observation that the bgwriter fails to call
AtEOXact_Files() after an error; therefore, if it gets an error while
holding an open DIR pointer, the DIR will never get closed. (There ar
