Re: Index corruption after pg_basebackup - Mailing list pgsql-admin

From Jorge Torralba
Subject Re: Index corruption after pg_basebackup
Date
Msg-id CACut7uTwWhXKHg+Fd3sy6hFnxWn58sLZPOr4frgrg23+NEgq-A@mail.gmail.com
Whole thread Raw
In response to Re: Index corruption after pg_basebackup  (Christoph Berg <myon@debian.org>)
Responses Re: Index corruption after pg_basebackup  (Christoph Berg <myon@debian.org>)
List pgsql-admin
Same on both systems.

 lc_collate  

-------------

 en_US.UTF-8

(1 row)


One of the failed index is

btree (account_id, lower(t1_type), t_id, "timestamp" DESC)


datatypes of:  UUID, text, text, timestamp




On Tue, Aug 28, 2018 at 9:42 AM Christoph Berg <myon@debian.org> wrote:
Re: Jorge Torralba 2018-08-28 <CACut7uRx72_R-nGOdOdnTSYCGGdKZ_TfsSghCb35+deF3s-4nw@mail.gmail.com>
> ERROR:  failed to re-find parent key in index "myindex" for deletion target
> page 851753

Which data type is that, and which LC_COLLATE setting is used?

If it's text (or similar), there's a known incompatibility with
de_DE.UTF-8 in different glibc versions. Possibly other locales and
libcs are affected as well.

Christoph


--
Thanks,

Jorge Torralba
----------------------------

Note: This communication may contain privileged or other confidential information. If you are not the intended recipient, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this email in error and delete the copy you received. Thank You.

pgsql-admin by date:

Previous
From: Ron
Date:
Subject: Re: More efficient pg_restore method?
Next
From: Evan Bauer
Date:
Subject: Re: More efficient pg_restore method?