From: | Patrick Molgaard <draaglom(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Multi-second pauses blocking even trivial activity |
Date: | 2018-09-08 00:32:36 |
Message-ID: | CA+Zan4vZRReeE0TP3nMBNZxe5DogZFXAeJStAZLw2RbE2B4WDQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Oh, to be clear - I'll be implementing your suggestion regardless, it seems
valuable whether or not it gets me closer to the root cause this time :)
I was just trying to dig into why it may be relevant -- I want to really
get a good grip on the mechanism behind this phenomenon.
Cheers
Patrick
On Fri, 7 Sep 2018, 20:20 Jeff Janes, <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Fri, Sep 7, 2018 at 2:03 PM Patrick Molgaard <draaglom(at)gmail(dot)com>
> wrote:
>
>>
>> Hi Jeff,
>>
>> Thanks for your reply. Are locks relevant in this case, though?
>>
>
> I don't know, but why theorize when we can know for sure? It at least
> invokes VirtualXactLockTableInsert. I don't see how that could block on a
> heavyweight lock, though. But again, why theorize when logging it is simple?
>
> Is it always the first statement in a connection which is blocking, or
> will established connections also block at the same time the new ones start
> to block?
>
> Cheers,
>
> Jeff
>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Molgaard | 2018-09-08 00:34:04 | Re: Multi-second pauses blocking even trivial activity |
Previous Message | Tim Cross | 2018-09-08 00:05:10 | Re: Performance of INSERT into temporary tables using psqlODBC driver |