Re: BUG #18830: ExecInitMerge Segfault on MERGE - Mailing list pgsql-bugs

From Amit Langote
Subject Re: BUG #18830: ExecInitMerge Segfault on MERGE
Date
Msg-id CA+HiwqFEehFAC1LJ+rd1gaP_uLO+GjkJ9YH_1dWfPANt+eibKQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18830: ExecInitMerge Segfault on MERGE  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-bugs
On Tue, Mar 18, 2025 at 4:52 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Tue, Mar 18, 2025 at 8:36 AM Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> > On Mon, 17 Mar 2025 at 12:21, Amit Langote <amitlangote09@gmail.com> wrote:
> > > If not, does the commit message look good to you?
> >
> > It could perhaps be more specific about saying that
> > ExecInitModifyTable() includes the first result relation if all others
> > have been pruned, so it isn't always included.
>
> Ok, done in the attached.
>
> I'll push this tomorrow.

Pushed after a few more tweaks to the commit message for better
logical flow, remove a redundant sentence.

Thanks a lot all for your help on this.

--
Thanks, Amit Langote



pgsql-bugs by date:

Previous
From: "谭忠涛"
Date:
Subject: The != and +/- signs are joined together as an operator
Next
From: Inzamam Shafiq
Date:
Subject: Possible bug acldefault function