| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Mark Zellers <mark(dot)zellers(at)workday(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: A modest proposal vis hierarchical queries: MINUS in the column list |
| Date: | 2021-06-08 16:28:47 |
| Message-ID: | 6f089eca-f04b-89d3-7c50-546fd29939c5@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.06.21 04:50, Julien Rouhaud wrote:
> On Mon, Jun 07, 2021 at 06:10:58PM -0400, Tom Lane wrote:
>>
>> I'm fairly disinclined to do anything about it though, because I'm
>> afraid of the SQL committee standardizing some other syntax for the
>> same idea in future (or maybe worse, commandeering the same keyword
>> for some other feature). It doesn't seem quite valuable enough to
>> take those risks for.
>
> Also, isn't the OP problem already solved by the SEARCH / CYCLE grammar
> handling added in 3696a600e2292?
You still get the path column in the output, which is what the OP didn't
want. But optionally eliminating the path column from the output might
be a more constrained problem to solve. We actually already discussed
this; we just need to do it somehow.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2021-06-08 16:37:46 | [PoC] Federated Authn/z with OAUTHBEARER |
| Previous Message | Robert Haas | 2021-06-08 16:26:02 | Re: Race condition in recovery? |