Re: Crash in new pgstats code
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
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:33:05Z
Lists: pgsql-hackers
Hi, On 2022-05-12 12:12:59 -0400, Tom Lane wrote: > 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 ;-). Those mostly were about stuff in 14 as well... I guess it'd be good to figure out precisely how the problem was triggered, but without further information I don't quite see how to figure it out... > But we have not seen any pgstat crashes lately, so I'm content to mark the > open item as resolved. Cool. Greetings, Andres Freund
Commits
-
pgstat: Use correct lock level in pgstat_drop_all_entries().
- 4a736a161c30 15.0 landed