| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: CREATE COLLATION definitional questions for ICU |
| Date: | 2017-06-30 17:38:12 |
| Message-ID: | fbcf5c00-340e-1294-01cf-dbebaca3088e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/25/17 11:45, Tom Lane wrote:
> * Now that it's possible for user-created collations to have encoding -1,
> I do not think that the "shadowing" tests in CollationCreate and
> IsThereCollationInNamespace are sufficient. They don't prevent a new
> collation with encoding -1 from shadowing an existing encoding-specific
> collation that doesn't happen to match the current DB's encoding.
> Now, you'd have to work at it for that to cause problems --- say,
> create such a situation in template0 and then copy template0 specifying
> that other encoding. But none of that is forbidden.
I see. Do you have an idea how to fix it without too much overhead? We
couldn't use the existing syscache for it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-30 18:04:56 | Re: CREATE COLLATION definitional questions for ICU |
| Previous Message | Peter Eisentraut | 2017-06-30 15:26:38 | Re: CREATE COLLATION definitional questions for ICU |