Horton

Re: Crash in new pgstats code

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>, Thomas Munro <thomas.munro@gmail.com>, Fujii Masao <fujii@postgresql.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-12T16:12:59Z
Lists: pgsql-hackers 
Andres Freund <andres@anarazel.de> writes:
> On 2022-05-11 15:46:13 +0900, Michael Paquier wrote:
>> Do we have anything remaining on this thread in light of the upcoming
>> beta1?  One fix has been pushed upthread, but it does not seem we are
>> completely in the clear either.

> I don't know what else there is to do, tbh.

Well, it was mostly you expressing misgivings upthread ;-).  But we
have not seen any pgstat crashes lately, so I'm content to mark the
open item as resolved.

			regards, tom lane

Commits

  1. pgstat: Use correct lock level in pgstat_drop_all_entries().