Re: [GENERAL] Changing collate & ctype for an existing database - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] Changing collate & ctype for an existing database
Date
Msg-id 19909.1499880683@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Changing collate & ctype for an existing database  (rihad <rihad@mail.ru>)
Responses Re: [GENERAL] Changing collate & ctype for an existing database  (rihad <rihad@mail.ru>)
Re: [GENERAL] Changing collate & ctype for an existing database  (rihad <rihad@mail.ru>)
List pgsql-general
rihad <rihad@mail.ru> writes:
> On 07/12/2017 01:54 PM, Albe Laurenz wrote:
>> As you see, your index is still sorted according to the C collation
>> and scanning it returns wrong results.

> This ordering issue can certainly be classified as an inconsistency, but
> nothing to lose sleep over. Is this all that is normally meant when
> saying "index corruption"?

Laurenz neglected to point out that if the index isn't sorted the way that
the system assumes it is, then searches may fail to find values that are
present (due to descending into the wrong subtree), and by the same token
insertions may fail to enforce uniqueness.  That's pretty corrupt in
my book.

            regards, tom lane


pgsql-general by date:

Previous
From: rihad
Date:
Subject: Re: [GENERAL] Changing collate & ctype for an existing database
Next
From: rihad
Date:
Subject: Re: [GENERAL] Changing collate & ctype for an existing database