Re: BUG #18871: Cross-partition MERGE fails with unclear internal error

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Tender Wang <tndrwang(at)gmail(dot)com>
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
Date: 2025-03-28 18:29:45
Message-ID: CAEZATCVg_9pUorFJxA2+RzVo1TEcgyPGSrk4gBojR2-NUH9HxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 28 Mar 2025 at 16:40, Tender Wang <tndrwang(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2025-03-29 02:39:12 Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
Previous Message Vinhson Nguyen 2025-03-28 18:24:22 PostgreSQL JDBC 42.7.5 returns an unexpected catalog name