Re: Aggregate ORDER BY patch - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Aggregate ORDER BY patch
Date
Msg-id 874oovjh5t.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Aggregate ORDER BY patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Aggregate ORDER BY patch
List pgsql-hackers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
Tom> I agree with Hitoshi that this seems to be a hack to deal with the[snip]

So copying the way that SELECT DISTINCT works would be the way to go?
i.e. keeping separate lists in the parse node for sorting and distinct?

What about error handling? If the user specifies agg(distinct x) where
x is not sortable, do we leave it to the planner to detect that (which
means not reporting the error position?)

-- 
Andrew.


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: named parameters in SQL functions
Next
From: Tom Lane
Date:
Subject: Re: Aggregate ORDER BY patch