| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN |
| Date: | 2011-03-22 21:47:55 |
| Message-ID: | 7640.1300830475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> On Tue, Mar 22, 2011 at 7:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Throw error for indeterminate collation of an ORDER/GROUP/DISTINCT target.
> hmm. In the current arrangement = doesn't depend on collation, right?
I've been trying to get rid of that assumption where I could.
I think it would probably be interesting if someday we could have
case-insensitive collations, for instance.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-03-22 23:12:05 | pgsql: Make FKs valid at creation when added as column constraints. |
| Previous Message | Greg Stark | 2011-03-22 21:44:06 | Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-03-22 22:06:02 | Re: 2nd Level Buffer Cache |
| Previous Message | Greg Stark | 2011-03-22 21:44:06 | Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN |