Lists: | pgsql-bugs |
---|
From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Documentation bug: reference to checkpoint activity in bgwriter |
Date: | 2012-01-01 01:54:53 |
Message-ID: | CAEYLb_VLiEgLdFkhr+KUzqaXYiCxVssTOt-F=F45n5u78Ec9dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
ISTM that the following reference, at config.sgml line 1345, ought to
be adjusted due to the introduction of the new checkpointer process:
Setting this to zero disables
background writing (except for checkpoint activity).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Documentation bug: reference to checkpoint activity in bgwriter |
Date: | 2012-01-09 18:47:03 |
Message-ID: | CA+TgmoayJNfecqRpfhLwgUo_Y_Kk8QG=6P+M=wGdhP1pJc7u6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> ISTM that the following reference, at config.sgml line 1345, ought to
> be adjusted due to the introduction of the new checkpointer process:
>
> Setting this to zero disables
> background writing (except for checkpoint activity).
Hmm, so what should we adjust it *to*?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Documentation bug: reference to checkpoint activity in bgwriter |
Date: | 2012-01-09 19:37:06 |
Message-ID: | CAEYLb_VTk=Rif+y1TOTr9wnz6EP47Gm5H3=WJhzNwFHqk=0mYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
On 9 January 2012 18:47, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
>> ISTM that the following reference, at config.sgml line 1345, ought to
>> be adjusted due to the introduction of the new checkpointer process:
>>
>> Setting this to zero disables
>> background writing (except for checkpoint activity).
>
> Hmm, so what should we adjust it *to*?
How about "Setting this to zero disables background writing. Note that
checkpoints, which are managed by a separate, dedicated auxiliary
process, are unaffected."
If this was the first release of Postgres, I'd suggest that we remove
any references to checkpoints, which are sort of orthogonal to the
stated main function of the bgwriter in past releases, which is to
clean dirty buffers so that backends don't have to. However, people
may still expect the bgwriter to manage checkpointing, particularly if
they're working off old sources of information, so it's useful to set
them straight.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Documentation bug: reference to checkpoint activity in bgwriter |
Date: | 2012-01-20 02:53:54 |
Message-ID: | CA+TgmoZ3WPNjB3e0P0iLPjoWr=yE5jEUBwEwArjeXaypBLS3Sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
On Mon, Jan 9, 2012 at 2:37 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> On 9 January 2012 18:47, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Sat, Dec 31, 2011 at 8:54 PM, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
>>> ISTM that the following reference, at config.sgml line 1345, ought to
>>> be adjusted due to the introduction of the new checkpointer process:
>>>
>>> Setting this to zero disables
>>> background writing (except for checkpoint activity).
>>
>> Hmm, so what should we adjust it *to*?
>
> How about "Setting this to zero disables background writing. Note that
> checkpoints, which are managed by a separate, dedicated auxiliary
> process, are unaffected."
>
> If this was the first release of Postgres, I'd suggest that we remove
> any references to checkpoints, which are sort of orthogonal to the
> stated main function of the bgwriter in past releases, which is to
> clean dirty buffers so that backends don't have to. However, people
> may still expect the bgwriter to manage checkpointing, particularly if
> they're working off old sources of information, so it's useful to set
> them straight.
OK, done.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Documentation bug: reference to checkpoint activity in bgwriter |
Date: | 2012-01-20 03:07:19 |
Message-ID: | CAEYLb_UEM6OTmWauLSF0niYPnna29crPZz9X_h3yO=W71agSrQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-bugs |
On 20 January 2012 02:53, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> OK, done.
Thanks
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services