| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Cybertec Schönig & Schönig GmbH <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Question about using ICU |
| Date: | 2020-09-28 09:45:17 |
| Message-ID: | 665E1A78-2B80-44A6-98AD-3644F1FD5F49@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Laurenz,
> On 28. Sep, 2020, at 11:04, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> There have been efforts to add this functionality:
> https://www.postgresql.org/message-id/flat/5e756dd6-0e91-d778-96fd-b1bcb06c161a%402ndquadrant.com
> but it didn't get done.
seems to be a rather complex thing according to the thread.
> Your best bet is to manually change the definition of all columns to use the new collation.
> psql's \gexec may help.
but then I'd have to do a reindex anyway, right? My goal was to avoid the reindex altogether, if possible.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2020-09-28 10:06:25 | how to switch off: WARNING: psql major version 11, server major version 13 |
| Previous Message | Laurenz Albe | 2020-09-28 09:17:39 | Re: Returning timestamp with timezone at specified timezone irrespective of client timezone |