From: | Holger Jakobs <holger(at)jakobs(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Problems with unique constraints |
Date: | 2023-01-26 12:42:24 |
Message-ID: | 47693153-3704-d084-fded-62ff16dadbf0@jakobs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Am 26.01.23 um 12:52 schrieb Massimo Ortensi:
>
> we had OS upgrades, but with the same locale.
>
> Is there any chance to avoid rebuilding of all indexes/constraints by
> checking the correctness of indexes ?
>
> *Massimo Ortensi - Responsabile ICT *
> logo <http://www.unimaticaspa.it/>
>
> Via Cristoforo Colombo, 21 - 40131, Bologna
> Tel. 051 4195069
> Cell. 3351092560
>
> _mortensi(at)unimaticaspa(dot)it <javascript:message_new('mailto',
> {mailto:'mortensi(at)unimaticaspa(dot)it', folder:'SU5CT1g=', msgid:'',
> subject: '', body:'0'})> _
>
In case of a change in the locale properties - albeit the name of the
locale remained the same - index corruption is possible.
This has been reported on RedHat platforms. The reaction of the
PostgreSQL project was to incorporate the locale libraries by ICU. They
can be used on demand. If they change, the database server will
automatically reindex if necessary.
If something in the OS libraries changes, the database server won't be
informed.
When indexes are corrupt (and data are fine), the best solution is to
reindex all indexes over varchar and text columns.
Kind Regards,
Holger
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2023-01-26 13:14:05 | Re: Problems with unique constraints |
Previous Message | Erik Wienhold | 2023-01-26 12:39:44 | Re: Problems with unique constraints |