From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | chris(at)withers(dot)org |
Cc: | bashtanov(at)imap(dot)cc, "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: debugging intermittent slow updates under higher load |
Date: | 2018-12-06 11:21:33 |
Message-ID: | CAFj8pRBERCvnjdVQiZTFwqa+==eHRhtsVf1QuOH66+mB28DPCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi
čt 6. 12. 2018 v 12:18 odesílatel Chris Withers <chris(at)withers(dot)org> napsal:
> On 06/12/2018 11:00, Alexey Bashtanov wrote:
> >
> >> I'm loath to start hacking something up when I'd hope others have done
> >> a better job already...
> > If you log all queries that take more than a second to complete, is your
> > update the only one logged, or something (the would-be blocker) gets
> > logged down together with it?
>
> Nope, only ones logged are these updates.
>
Can you check latency on file system? Some latencies can be enforced by
overloaded file system due wrong configuration of file system cache.
https://serverfault.com/questions/471070/linux-file-system-cache-move-data-from-dirty-to-writeback
Regards
Pavel
> Chris
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Johann Spies | 2018-12-06 13:43:17 | How to build a btree index with integer values on jsonb data? |
Previous Message | Chris Withers | 2018-12-06 11:18:25 | Re: debugging intermittent slow updates under higher load |