Re: BUG #18871: Cross-partition MERGE fails with unclear internal error - Mailing list pgsql-bugs

From Dean Rasheed
Subject Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
Date
Msg-id CAEZATCVg_9pUorFJxA2+RzVo1TEcgyPGSrk4gBojR2-NUH9HxQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18871: Cross-partition MERGE fails with unclear internal error  (Tender Wang <tndrwang@gmail.com>)
Responses Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
List pgsql-bugs
On Fri, 28 Mar 2025 at 16:40, Tender Wang <tndrwang@gmail.com> wrote:
>
> I tried a quick fix by adding "case CMD_NOTHING" after "case CMD_DELETE" like below:
>
> case CMD_DELETE:
> case CMD_NOTHING:
>        break;
>
> It can work, and all regression tests pass.  But I don't look into more details.  This solution may not fix the root
cause.

Yes, that looks like the right fix.

This appears to be a trivial oversight in ExecInitPartitionInfo(). I
did a quick scan of other places that look at action->commandType and
I didn't see any others that overlook CMD_NOTHING.

Regards,
Dean



pgsql-bugs by date:

Previous
From: Vinhson Nguyen
Date:
Subject: PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
Next
From: Tender Wang
Date:
Subject: Re: BUG #18871: Cross-partition MERGE fails with unclear internal error