From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Spurious pgstat_drop_replslot() call |
Date: | 2024-03-12 22:37:22 |
Message-ID: | ZfDZIgkzQnkPpGsC@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 12, 2024 at 12:00:00PM +0300, Alexander Lakhin wrote:
> Sorry for a bit off-topic, but I've remembered an anomaly with a similar
> assert:
> https://www.postgresql.org/message-id/17947-b9554521ad963c9c%40postgresql.org
Thanks for the reminder. The invalidation path with the stats drop is
only in 16~.
> Maybe you would find it worth considering while working in this area...
> (I've just run that reproducer on b36fbd9f8 and confirmed that the
> assertion failure is still here.)
Indeed, something needs to happen. I am not surprised that it still
reproduces; nothing has changed with the locking of the stats entries.
:/
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2024-03-12 22:43:03 | Re: [EXTERNAL] Re: Add non-blocking version of PQcancel |
Previous Message | Thomas Munro | 2024-03-12 21:53:40 | Recent 027_streaming_regress.pl hangs |