Re: View with duplicate GROUP BY entries - Mailing list pgsql-hackers

From Robert Haas
Subject Re: View with duplicate GROUP BY entries
Date
Msg-id CA+TgmoY6Jn67wBdU9pzgYhNLV33kAYenQUV6VqD02HXjQah5-w@mail.gmail.com
Whole thread Raw
In response to Re: View with duplicate GROUP BY entries  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: View with duplicate GROUP BY entries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Nov 21, 2017 at 12:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> writes:
>> While reviewing patch for similar problem in postgres_fdw [1], I
>> noticed that we don't use positional notation while creating the view.
>> This might introduced anomalies when GROUP BY entries are
>> non-immutable.
>
> Yeah, we probably ought to make more of an effort to regenerate the
> original query wording.  I do not think that forcing positional notation
> is a suitable answer in this case, because it would result in converting
> SQL-standard queries to nonstandard ones.

Who cares?  The other end is presumptively PostgresSQL, because this
is postgres_fdw.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] Custom compression methods
Next
From: Robert Haas
Date:
Subject: Re: feature request: consume asynchronous notification via a function