| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: collations in shared catalogs? |
| Date: | 2015-02-25 21:19:45 |
| Message-ID: | 20150225211945.GC24199@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-02-25 15:59:55 -0500, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > On 2015-02-25 12:08:32 -0500, Tom Lane wrote:
> >> The most obvious fix is to change "provider" to a NAME column.
>
> > Yea. I'm not sure why that wasn't done initially. I can't really see the
> > length be an issue. How about we add an error check enforcing ascii,
> > that'll work in the back branches?
>
> Nope, that won't help much at all. C vs en_US for instance is different
> sort orders even with all-ASCII data.
Ick, yes. The restriction to a charset that's encodable in all server
encodings should be there additionally, but it's not sufficient :(
> Basically you're screwed if you've got different collations in different
> databases and you put anything into pg_shseclabel ...
Hrmpf.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-02-25 22:04:55 | Re: INSERT ... ON CONFLICT UPDATE and logical decoding |
| Previous Message | Tom Lane | 2015-02-25 20:59:55 | Re: collations in shared catalogs? |