| From: | "Tomas Vondra" <tv(at)fuzzy(dot)cz> |
|---|---|
| To: | "Tomas Vondra" <tv(at)fuzzy(dot)cz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PATCH: regular logging of checkpoint progress |
| Date: | 2011-09-01 19:59:56 |
| Message-ID: | 14933e7d24533b829c198e0d8c7b5ad3.squirrel@sq.gransy.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've prepared a significantly simplified version of the patch. The two
main changes are
(a) it does not update the pg_stat_bgwriter anymore, it just prints an
info to the server log
(b) a new GUC is not required, it's driven by the log_checkpoints
This version will log at least 10 'checkpoint status' lines (at 10%, 20%,
30%, ...) and whenever 5 seconds since the last log elapses. The time is
not checked for each buffer but for 128 buffers.
So if the checkpoint is very slow, you'll get a message every 5 seconds,
if it's fast you'll get 10 messages.
Tomas
| Attachment | Content-Type | Size |
|---|---|---|
| checkpoint-stats-update-v2.diff | text/plain | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2011-09-01 21:44:16 | Re: sha1, sha2 functions into core? |
| Previous Message | Robert Haas | 2011-09-01 19:26:21 | Re: postgresql.conf archive_command example |