From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Publish checkpoint timing and sync files summary data to pg_stat_bgwriter |
Date: | 2012-01-19 16:56:31 |
Message-ID: | CA+U5nMKrUG5OB8SmMEHs-YqGFcbJcS0wBSwaRn2HKiikm_HBiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 19, 2012 at 3:52 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> And, it doesn't seem like it's necessarily going to safe me a whole
> lot either, because if it turns out that my sync phases are long, the
> first question out of my mouth is going to be "what percentage of my
> total sync time is accounted for by the longest sync?". And so right
> there I'm back to the logs.
It seems clear that the purpose of this is to quickly and easily
decide whether there is a potential problem.
If you decide there is a potential problem, you may wish to look at
more detailed information.
So there is a huge time saving from avoiding the need to look at the
detail when its unnecessary and possibly not even enabled.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2012-01-19 17:12:02 | Re: Inline Extension |
Previous Message | Simon Riggs | 2012-01-19 16:46:02 | Re: Simulating Clog Contention |