From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: "variable not found in subplan target list"
In-reply-to: <20230328112248.6as34mlx5sr4kltg@alvherre.pgsql>
References: <20230328112248.6as34mlx5sr4kltg@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Tue, 28 Mar 2023 13:22:48 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3460254.1680008201.1@sss.pgh.pa.us>
Date: Tue, 28 Mar 2023 08:56:41 -0400
Message-ID: <3460255.1680008201@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3460255.1680008201%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I have to run now so can't dissect it, but while running sqlsmith on the
> SQL/JSON patch after Justin's report, I got $SUBJECT in this query:

I reduced this down to

MERGE INTO public.target_parted as target_0
    USING public.itest1 as ref_0
    ON target_0.b = ref_0.a
    WHEN NOT MATCHED
       THEN INSERT VALUES (42, 13);

The critical moving part seems to just be that the MERGE target
is a partitioned table ... but surely somebody tested that before?

			regards, tom lane