| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Amit Kapila <akapila(at)postgresql(dot)org> |
| Subject: | Re: pg15b3: crash in parallel vacuum |
| Date: | 2022-08-18 23:04:47 |
| Message-ID: | 20220818230447.GP26426@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 18, 2022 at 09:52:36AM -0500, Justin Pryzby wrote:
> On Thu, Aug 18, 2022 at 11:24:22PM +0900, Masahiko Sawada wrote:
> > The status = 11 is invalid value. Probably because indstats was not
> > initialized to 0 as I mentioned.
> >
> > Justin, if it's reproducible in your environment, could you please try
> > it again with the attached patch?
>
> Yes, this seems to resolve the problem.
It seems a bit crazy that this escaped detection until now.
Are these allocations especially vulnerable to uninitialized data ?
--
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-08-18 23:05:57 | Re: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Thomas Munro | 2022-08-18 22:52:54 | Re: s390x builds on buildfarm |