| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| 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 20:59:55 |
| Message-ID: | 818.1424897995@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Basically you're screwed if you've got different collations in different
databases and you put anything into pg_shseclabel ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-02-25 21:19:45 | Re: collations in shared catalogs? |
| Previous Message | Tomas Vondra | 2015-02-25 20:56:11 | Re: a fast bloat measurement tool (was Re: Measuring relation free space) |