| From: | Richard van der Hoff <richard(at)matrix(dot)org> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Inexplicable duplicate rows with unique constraint |
| Date: | 2020-01-16 17:28:46 |
| Message-ID: | e2dbb06e-b314-88ca-e513-af4a31c2f99b@matrix.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 16/01/2020 17:24, Daniel Verite wrote:
> Looking at these columns which are of type text but do not
> contain words of any particular language, there's probably
> no point in using a linguistic-aware collation for them.
>
> If you maintain the database schema, what you could do to avoid
> the dependency on the OS collation and stay clear of the particular
> upgrade difficulty of collations is to use COLLATE "C" for this kind of
> field, as opposed to the default collation of the database.
> As a bonus, operations with the "C" collations tend to be faster,
> sometimes even much faster.
Good to know, thanks Daniel!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard van der Hoff | 2020-01-16 17:31:38 | Re: Inexplicable duplicate rows with unique constraint |
| Previous Message | Adrian Klaver | 2020-01-16 17:27:25 | Re: Inexplicable duplicate rows with unique constraint |