From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | Marc Cousin <cousinmarc(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8 |
Date: | 2020-07-02 16:51:24 |
Message-ID: | 857178.1593708684@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
[ just to tie back to this old thread ]
I wrote:
> I poked into this area for awhile, and it turns out to be even a
> worse can of worms than I thought. I looked through gram.y and
> parse_expr.c, and identified several distinct classes of issue.
> (I'm not promising that I found everything.)
In fact, the thread at [1] identifies an essentially similar class
of issue that I missed: JOIN ... USING (x) also implicitly looks up
an equality operator by seeing what "tab1.x = tab2.x" resolves as.
This is much like the CASE situation, in that there's no
SQL-standard-compliant way to reverse-list a view containing
such a construct while showing how it was resolved. We'd need
to invent some new syntax if we want to make this safer.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-07-02 22:28:20 | Re: BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition |
Previous Message | Etsuro Fujita | 2020-07-02 11:52:23 | Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2020-07-02 17:09:57 | Re: proposal: unescape_text function |
Previous Message | Tom Lane | 2020-07-02 16:41:22 | Re: Sync vs Flush |