MIME-Version: 1.0
References: <19460-5625143cef66012f@postgresql.org> <53936.1776633020@sss.pgh.pa.us>
 <CAMbWs48E2qqd4B6AdvJDyPBi685-_bDEvoe0aJnYzAPL1v30zg@mail.gmail.com> <81857.1776648374@sss.pgh.pa.us>
In-Reply-To: <81857.1776648374@sss.pgh.pa.us>
From: Richard Guo <guofenglinux@gmail.com>
Date: Mon, 20 Apr 2026 11:17:47 +0900
Message-ID: <CAMbWs49PPxhrqBjHj3Wy4hK4=_DoHkJdAHL_q1mqpyyCk5MdMw@mail.gmail.com>
Subject: Re: BUG #19460: FULL JOIN rewriting issue on empty queries
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: francois.jehl@pigment.com, pgsql-bugs@lists.postgresql.org, 
	Robert Haas <robertmhaas@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAMbWs49PPxhrqBjHj3Wy4hK4%3D_DoHkJdAHL_q1mqpyyCk5MdMw%40mail.gmail.com>
Precedence: bulk

On Mon, Apr 20, 2026 at 10:26=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote=
:
> Thanks for looking at it!  There is a loose end still bothering me:
> if you remove the lower "WHERE t.id =3D ..." clause, or change it to be
> something other than an equality constraint on t.id, the bug doesn't
> manifest.  The reason for that is un-obvious.

The reason seems to be that the equality constraint is a restriction
clause for the inner relation 't', and is needed to determine that the
relation has a matching unique index and is therefore distinct.  If we
remove it, or change it to something that isn't mergejoinable, we
won't be able to prove the inner side of the left join is distinct,
and thus won't be able to remove that left join.

I think the qual clause "sub.id =3D empty_source.id" might be confusing,
because empty_source.id is constant NULL, and this clause would be
simplified to constant NULL during const-folding.

- Richard