From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: checkpoints taking much longer than expected |
Date: | 2019-06-16 17:37:02 |
Message-ID: | 20190616173702.GQ2480@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Jeff Janes (jeff(dot)janes(at)gmail(dot)com) wrote:
> On Sat, Jun 15, 2019 at 4:50 AM Tiemen Ruiten <t(dot)ruiten(at)tech-lab(dot)io> wrote:
> > On Fri, Jun 14, 2019 at 5:43 PM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> >> The time information is all there and it tells you what it's doing and
> >> how much had to be done... If you're unhappy with how long it takes to
> >> write out gigabytes of data and fsync hundreds of files, talk to your
> >> storage people...
>
> Right, but true only because they were "checkpoint starting: immediate".
> Otherwise the reported write time includes intentional sleeps added to
> honor the checkpoint_completion_target. A bit confusing to report it that
> way, I think.
Hrmpf, yeah, we could probably improve on that, I'd certainly like to
see that broken out.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2019-06-16 18:12:50 | Re: bug regclass::oid |
Previous Message | Stephen Frost | 2019-06-16 17:30:28 | Re: checkpoints taking much longer than expected |