Re: Outputting Standard SQL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Outputting Standard SQL
Date
Msg-id 30913.1566760486@sss.pgh.pa.us
Whole thread Raw
In response to Outputting Standard SQL  (Vik Fearing <vik.fearing@2ndquadrant.com>)
Responses Re: Outputting Standard SQL
List pgsql-hackers
Vik Fearing <vik.fearing@2ndquadrant.com> writes:
> EXPLAIN (COSTS OFF) SELECT * FROM pg_am WHERE amname LIKE '%t%';
>             QUERY PLAN            
> -----------------------------------
>  Seq Scan on pg_am
>    Filter: (amname ~~ '%t%'::text)
> (2 rows)

> Why don't we convert that back to LIKE?

Trying to do so would make our schema-qualification problems worse
not better.  See

https://www.postgresql.org/message-id/flat/ffefc172-a487-aa87-a0e7-472bf29735c8%40gmail.com

particularly

https://www.postgresql.org/message-id/10492.1531515255@sss.pgh.pa.us

We really need to invent some weird nonstandard syntax for IS DISTINCT
FROM and related cases, in order to not have broken dump/reload scenarios.
I'd just as soon not do that for LIKE, when the operator syntax serves
well enough.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Quentin Rameau
Date:
Subject: Re: [PATCH] Fix missing argument handling in psql getopt
Next
From: Quentin Rameau
Date:
Subject: Re: [PATCH] Fix missing argument handling in psql getopt