On 09/06/10 15:04, Kevin Grittner wrote:
> Magnus Hagander wrote:
>> The way to provoke the problem is:
>
> The way I ran into it was to have a web application which only ran
> read-only transactions. Sooner or later it would need to write a
> page from the buffer to make space to read a new page, and then it
> would forever be holding a WAL file open, even after it was deleted.
>
> Previous thread on the topic starts here:
>
> http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php
>
> continuing here:
>
> http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php
>
> Resulting in a TODO listed with this description:
>
> Close deleted WAL files held open in *nix by long-lived read-only
> backends
This patch only helps with walwriter, though, not backends. Your
scenario is probably even more common, but will need a different fix.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com