From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Subject: | Re: WITH clause in CREATE STATISTICS |
Date: | 2017-05-11 17:08:38 |
Message-ID: | 20170511170838.qlohfmvzrvv6or26@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Hmm ... I'm not sure that I buy that particular argument. If you're
> concerned that the grammar could not handle "FROM x JOIN y USING (z)",
> wouldn't it also have a problem with "FROM x JOIN y ON (z)"?
>
> It might work anyway, since the grammar should know whether ON or USING
> is needed to complete the JOIN clause. But I think you'd better check
> whether the complete join syntax works there, even if we're not going
> to support it now.
Tomas spent some time trying to shoehorn the whole join syntax into the
FROM clause, but stopped once he realized that the joined_table
production uses table_ref, which allow things like TABLESAMPLE, SRFs,
LATERAL, etc which presumably we don't want to accept in CREATE STATS.
I didn't look into it any further. But because of the other
considerations, I did end up changing the ON to FOR.
So the attached is the final version which I intend to push shortly.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
createstats-with-2.patch | text/plain | 49.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-05-11 17:13:52 | Re: Time based lag tracking for logical replication |
Previous Message | Simon Riggs | 2017-05-11 16:49:32 | Re: Safer and faster get_attstatsslot() |