Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
Date: 2023-07-26 05:55:23
Message-ID: CAD21AoAHj4m-emE8U48PpqJzOs22NWJJ5on+RWWGLVJPpOQCUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jul 26, 2023 at 1:27 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> On 2023-07-25 16:35:54 +0900, Masahiko Sawada wrote:
> > Thank you for your confirmation. I can push the fix if you're okay.
> > I've attached the patch.
>
> LGTM.

Thank you for reviewing it! Pushed, and marked as resolved in the open
items page.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro Horiguchi 2023-07-26 08:36:00 Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Previous Message PG Bug reporting form 2023-07-26 04:34:29 BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.