Peter Geoghegan writes:
> On Wed, May 25, 2016 at 7:12 PM, Andres Freund <andres@anarazel.de> wrote:
>>
>> =# CREATE TABLE twocol(col01 int, col02 int);
>> =# SELECT DISTINCT col01, col02, col01 FROM twocol ;
>> ERROR: XX000: ORDER/GROUP BY expression not found in targetlist
>> LOCATION: get_sortgroupref_tle, tlist.c:341
>>
>> which appears to be a 9.6 regression, presumable fallout from the path
>> restructuring.
>
> It's surprising that SQL Smith didn't catch something with such simple
> steps to reproduce.
I removed distinct relatively early because it causes a large part of
queries to fail due to it not finding an equality operator it likes. It
seems to be more picky about the equality operator than, say, joins.
I'm sure it has a good reason to do so?
regression=> select distinct f1 from path_tbl;
ERROR: could not identify an equality operator for type path
LINE 1: select distinct f1 from path_tbl;
regression=> \do =
-[ RECORD 38 ]-+----------------------------
Schema | pg_catalog
Name | =
Left arg type | path
Right arg type | path
Result type | boolean
Description | equal
