Re: Odd error when using UNION and COLLATE

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Odd error when using UNION and COLLATE
Date: 2016-07-20 22:06:17
Message-ID: 20160720220617.GJ24559@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 20, 2016 at 06:03:08PM -0400, Tom Lane wrote:
> Greg Stark <stark(at)mit(dot)edu> writes:
> > But I think I agree that it's surprising that the collate clause isn't
> > working in the ORDER BY on a column produced by a UNION. Certainly
> > that's where people usually want to put it.
>
> See this ancient comment in transformSetOperationStmt:
>
> * For now, we don't support resjunk sort clauses on the output of a
> * setOperation tree --- you can only use the SQL92-spec options of
> * selecting an output column by name or number. Enforce by checking that
> * transformSortClause doesn't add any items to tlist.
>
> Perhaps sometime we ought to make an effort to relax that.

Oh, I didn't see that above the error block.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-07-20 23:04:54 Re: Design for In-Core Logical Replication
Previous Message Bruce Momjian 2016-07-20 22:05:22 Re: Odd error when using UNION and COLLATE