| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: LockHasWaiters() crashes on fast-path locks |
| Date: | 2026-09-02 04:55:38 |
| Message-ID: | apesSthBQ_0CA7yR@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 02, 2026 at 08:53:47AM +0900, Michael Paquier wrote:
> Perhaps out-of-core code or extensions could make use of this API, but
> in my experience this usually points at possible optimizations in the
> backend core code. I'd suggest to look at that first, perhaps, if
> you'd like to make LockHasWaiters() fast-path safe?
Oh, I have missed the argument about autoprewarm and pg_prewarm on
this thread:
https://www.postgresql.org/message-id/CALj2ACXXx9TwYzeP0cRnZKHz60yOYivcG7yiV=2FTC5chSVoOg@mail.gmail.com
Sorry about that. I'd be curious about a different case where this
could be used. Without the other proposal this feels a bit dead when
taken independently..
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | surya poondla | 2026-09-02 05:02:36 | Re: Introduce XID age based replication slot invalidation |
| Previous Message | Bertrand Drouvot | 2026-09-02 04:34:19 | Re: pgstat: Flush some statistics within running transactions, take 2 |