| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remove checkpoint_warning |
| Date: | 2016-07-09 20:59:45 |
| Message-ID: | 20160709205945.dtggbcuvnumyq4v4@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-07-09 16:46:32 -0400, Alvaro Herrera wrote:
> the checkpoint_warning feature was added by commit 2986aa6a668bce3cfb836
> in November 2002 when we didn't have any logging of checkpointing at
> all. I propose to remove it: surely anyone who cares about analyzing
> checkpointing behavior nowadays is using the log_checkpoint feature
> instead, which contains much more detail. The other one is just noise
> now, and probably ignored amidst the number of other warning traffic.
I think we could do that, if we enable log_checkpoints by default, but
right now we don't...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-09 21:12:15 | Re: remove checkpoint_warning |
| Previous Message | Tom Lane | 2016-07-09 20:50:07 | Re: [CF2016-9] Allow spaces in working path on tap-tests |