From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Improving collation-dependent indexes in system catalogs |
Date: | 2018-12-15 18:31:29 |
Message-ID: | 17666.1544898689@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> While fooling with the idea of making type "name" collation
> aware, it occurred to me that there's a better, more general
> answer, which is to insist that collation-aware system catalog
> columns must be marked with C collation. This rule would apply
> without modification to both "text" and "name" columns. In the
> wake of commit 5e0928005, it also means that pg_statistic data
> for such a column would port safely across a database collation
> change, which up to now it does not. And I think we could have
> the bootstrap code apply the rule automatically, making for one
> less way to screw up when changing catalog definitions.
Concretely, this ...
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
use-c-collation-in-catalogs-1.patch | text/x-diff | 11.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-12-15 18:44:48 | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
Previous Message | Hugh Ranalli | 2018-12-15 18:08:00 | Re: BUG #15548: Unaccent does not remove combining diacritical characters |