Andrew Gierth <and...@tao11.riddles.org.uk> writes:
> This doesn't seem to present any problems as far as the syntax goes,
> and the actual execution is just a small matter of coding, but I'm not
> seeing the best way to handle it in parse-analysis. All the existing
> infrastructure for ORDER BY seems to be dependent on targetlists, which
> obviously we don't have in the context of an aggregate call.
Well, if you don't want to refactor that code, it wouldn't be difficult
to make a one-entry tlist containing the aggregate argument, and then
throw it away again after you'd extracted what you need.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
