Re: BUG #18830: ExecInitMerge Segfault on MERGE

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, tharakan(at)gmail(dot)com
Subject: Re: BUG #18830: ExecInitMerge Segfault on MERGE
Date: 2025-03-19 03:16:54
Message-ID: CA+HiwqFEehFAC1LJ+rd1gaP_uLO+GjkJ9YH_1dWfPANt+eibKQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 18, 2025 at 4:52 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> On Tue, Mar 18, 2025 at 8:36 AM Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> > On Mon, 17 Mar 2025 at 12:21, Amit Langote <amitlangote09(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Inzamam Shafiq 2025-03-19 12:49:14 Possible bug acldefault function
Previous Message 谭忠涛 2025-03-19 01:23:33 The != and +/- signs are joined together as an operator