Re: bgwriter leaks resources after errors - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Re: bgwriter leaks resources after errors
Date
Msg-id dna0dh$1lrp$1@news.hub.org
Whole thread Raw
In response to bgwriter leaks resources after errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> 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 pinned? Then 
remember that buffer is enough. This could avoid using ResourceOwner but it 
may need some hack into pin/unpin.

Regards,
Qingqing 




pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: HOOKS for Synchronous Replication?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: generalizing the planner knobs