Am Mon, Nov 14, 2022 at 05:42:16PM +0100 schrieb Daniel Verite:
> > Which is why my question still stands: does the above
> > three-strikes operation safely take care of any collation
> > issues that may currently exist in a database ?
>
> For the indexes, yes, but theorically, all constraints inv
Karsten Hilbert wrote:
> Which is why my question still stands: does the above
> three-strikes operation safely take care of any collation
> issues that may currently exist in a database ?
For the indexes, yes, but theorically, all constraints involving collatable
types need a recheck.
F
Le lun. 14 nov. 2022 à 13:10, Julien Rouhaud a écrit :
> yes exactly. but it's likely that people will have some form of automation
>> to run the reindex if there's any discrepancy between the recorded
>> collation version and recorded version,
>
>
sorry I meant "and the current version"
>
Le lun. 14 nov. 2022 à 05:58, Karsten Hilbert a
écrit :
> Am Sun, Nov 13, 2022 at 12:46:53PM -0800 schrieb Christophe Pettus:
>
> > > On Nov 13, 2022, at 12:45, Karsten Hilbert
> wrote:
> > > REINDEX DATABASE db_in_question;
> > > ALTER DATABASE db_in_question REFRESH COLLATION VERSION;
Am Sun, Nov 13, 2022 at 12:46:53PM -0800 schrieb Christophe Pettus:
> > On Nov 13, 2022, at 12:45, Karsten Hilbert wrote:
> > REINDEX DATABASE db_in_question;
> > ALTER DATABASE db_in_question REFRESH COLLATION VERSION;
> > ALTER COLLATION every_collation_from_pg_collation REFRESH VER
> On Nov 13, 2022, at 12:45, Karsten Hilbert wrote:
> REINDEX DATABASE db_in_question;
> ALTER DATABASE db_in_question REFRESH COLLATION VERSION;
> ALTER COLLATION every_collation_from_pg_collation REFRESH VERSION;
I may be totally off-base here, but shouldn't the REINDEX be
