Re: Killing off removed rels properly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Killing off removed rels properly
Date: 2023-02-20 16:33:28
Message-ID: 3582657.1676910808@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Lakhin <exclusion(at)gmail(dot)com> writes:
> After this change the following query triggers an assert:

> CREATE TABLE tt (tid integer PRIMARY KEY) PARTITION BY LIST (tid);
> CREATE TABLE ttp PARTITION OF tt DEFAULT;
> CREATE TABLE st (sid integer);

> MERGE INTO tt USING st ON tt.tid = st.sid WHEN NOT MATCHED THEN INSERT
> VALUES (st.sid);

Hmph. Yeah, I think that's just wrong: the cases of found-a-baserel
and didn't-find-a-baserel should be treating MERGE-rejection identically.
This is probably broken even before e9a20e451.

Thanks for the report!

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Imseih (AWS), Sami 2023-02-20 16:47:58 Re: Add index scan progress to pg_stat_progress_vacuum
Previous Message Justin Pryzby 2023-02-20 16:31:11 Re: add PROCESS_MAIN to VACUUM