Re: Index corruption after pg_basebackup

From: Jorge Torralba <jorge(dot)torralba(at)gmail(dot)com>
To: myon(at)debian(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: Index corruption after pg_basebackup
Date: 2018-08-28 17:03:38
Message-ID: CACut7uTwWhXKHg+Fd3sy6hFnxWn58sLZPOr4frgrg23+NEgq-A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)debian(dot)org> wrote:

> Re: Jorge Torralba 2018-08-28 <
> CACut7uRx72_R-nGOdOdnTSYCGGdKZ_TfsSghCb35+deF3s-4nw(at)mail(dot)gmail(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Evan Bauer 2018-08-28 17:13:08 Re: More efficient pg_restore method?
Previous Message Ron 2018-08-28 17:00:24 Re: More efficient pg_restore method?