| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BGWriter latch, power saving |
| Date: | 2012-01-27 07:16:52 |
| Message-ID: | 4F224F64.7000100@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26.01.2012 21:37, Peter Geoghegan wrote:
> On 26 January 2012 16:48, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Ok, committed with some further cleanup.
>>
>> Do you think the docs need to be updated for this, and if so,
>> where? The only place I found in the docs that speak about how the
>> bgwriter works is in config.sgml, where bgwriter_delay is
>> described. Want to suggest an update to that?
>
> This new behaviour might warrant a mention, as in the attached
> doc-patch.
Hmm, the word "hibernate" might confuse people in this context. I
committed this as:
> It then sleeps for <varname>bgwriter_delay</> milliseconds, and
> repeats. When there are no dirty buffers in the buffer pool, though,
> it goes into a longer sleep regardless of <varname>bgwriter_delay</>.
Thanks!
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2012-01-27 08:57:01 | Re: Speed dblink using alternate libpq tuple storage |
| Previous Message | Kyotaro HORIGUCHI | 2012-01-27 04:45:15 | Re: Speed dblink using alternate libpq tuple storage |