Re: strange slow query - lost lot of time somewhere

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: strange slow query - lost lot of time somewhere
Date: 2022-05-06 05:35:50
Message-ID: CAFj8pRCgTcfMPHtJCa7uaPW-MCEGRAobyAYowoabRa-0DjMGEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pá 6. 5. 2022 v 1:28 odesílatel David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> napsal:

> On Mon, May 2, 2022 at 10:02 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
>
>>
>>
>> út 3. 5. 2022 v 6:57 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>>
>>> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>>> > there is really something strange (see attached file). Looks so this
>>> issue
>>> > is much more related to planning time than execution time
>>>
>>> You sure there's not something taking an exclusive lock on one of these
>>> tables every so often?
>>>
>>
>> I am almost sure, I can see this issue only every time when I set a
>> higher work mem. I don't see this issue in other cases.
>>
>>>
>>>
> What are the values of work_mem and hash_mem_multiplier for the two cases?
>

(2022-05-06 07:35:21) prd_aukro=# show work_mem ;
┌──────────┐
│ work_mem │
├──────────┤
│ 400MB │
└──────────┘
(1 řádka)

Čas: 0,331 ms
(2022-05-06 07:35:32) prd_aukro=# show hash_mem_multiplier ;
┌─────────────────────┐
│ hash_mem_multiplier │
├─────────────────────┤
│ 1 │
└─────────────────────┘
(1 řádka)

> David J.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-05-06 05:52:14 Re: strange slow query - lost lot of time somewhere
Previous Message Tom Lane 2022-05-06 03:57:28 Re: failures in t/031_recovery_conflict.pl on CI