On Thu, Feb 9, 2023 at 3:55 PM Paul McGarry wrote:
> Will the amcheck reliably identify all issues that may arise from a collation
> change?
Theoretically it might not. In practice I'd be very surprised if it
ever failed to detect such an inconsistency. If you want to be extra
careful, and can a
Hi Peter,
Thanks for your input, I'm feeling more comfortable that I correctly
understand the problem now and it's "just" a collation related issue.
> I recommend running amcheck on all indexes, or at least all
> possibly-affected text indexes.
>
>
Will the amcheck reliably identify all issues t
On Wed, Feb 8, 2023 at 11:54 PM Paul McGarry wrote:
> But if it is the problem, why did the update start working after I recreated
> the other index?
There is no reason why reindexing another index ought to have had that
effect. The likely explanation is that subsequent updates used a
successor
On 2/8/23 23:53, Paul McGarry wrote:
I have three databases, two of databases where I am experiencing the
issue below.
The first database was created from a dump in Feb 2022 (a few weeks
after the time period for which I seem to have problematic indexes, maybe).
The second database was then cl
