Re: Schema-qualify the equality operator when deparsing NULLIF/IS DISTINCT FROM

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: michal.dtz@gmail.com
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-07-07T14:27:24Z
Lists: pgsql-hackers
michal.dtz@gmail.com writes:
> Attached is v2, which takes the opposite approach: instead of teaching
> the deparser to avoid the constructs, it gives every construct that
> resolves an operator by unqualified name a place to write a
> schema-qualified one.  That covers the full list you cataloged back in
> 2018 (10492.1531515255@sss.pgh.pa.us) -- IS [NOT] DISTINCT FROM,
> NULLIF, simple CASE, row comparisons, ANY/ALL subquery comparisons --
> plus JOIN USING / NATURAL JOIN, which has the same disease.

I didn't read the patch yet, but this sounds promising.

> If the direction looks right I will register this in the next
> commitfest (PG 20-1).

Next one is already 20-2, but please do register it.

			regards, tom lane