| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dirk Mika <Dirk(dot)Mika(at)mikatiming(dot)de>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Set COLLATE on a session level |
| Date: | 2020-12-05 12:12:15 |
| Message-ID: | 67253506-9381-44ac-0bbd-5b4aea29cc19@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2020-12-04 17:18, Tom Lane wrote:
>> There is a SET COLLATION command in the SQL standard that does this.
>> Someone just has to implement it. It wouldn't be terribly difficult, I
>> think.
>
> [ squint... ] Just because it's in the standard doesn't mean it's a
> good idea. It sounds like this is morally equivalent to a GUC that
> changes query semantics. We have learned painfully that such behaviors
> are best avoided, because they break things you didn't expect to break.
I think it would be analogous to the schema search path.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2020-12-05 14:18:29 | Aw: Re: Set COLLATE on a session level |
| Previous Message | Alban Hertroys | 2020-12-05 11:44:15 | Re: Accessing Postgres Server and database from other Machine |