| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Fujii Masao <fujii(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Crash in new pgstats code |
| Date: | 2022-05-12 16:12:59 |
| Message-ID: | 381855.1652371979@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-05-12 16:33:05 | Re: Crash in new pgstats code |
| Previous Message | Tom Lane | 2022-05-12 15:59:49 | Re: Mark all GUC variable as PGDLLIMPORT |