Re: pg_stat_statements locking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_statements locking
Date: 2022-09-12 18:01:23
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
>> On 12 Sep 2022, at 18:18, Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>> That being
>> said I don't know if adding a timeout would be too expensive for the lwlock
>> infrastructure.

I want to object fiercely to loading down LWLock with anything like
timeouts. It's supposed to be "lightweight". If we get away from
that we're just going to find ourselves needing another lighter-weight
lock mechanism.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-09-12 18:01:49 Re: PostgreSQL 15 release announcement draft
Previous Message Peter Eisentraut 2022-09-12 17:59:36 Re: Convert *GetDatum() and DatumGet*() macros to inline functions