From: | "Andrus" <kobruleht2(at)hot(dot)ee> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Adrian Klaver" <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query returns no rows in pg_basebackup cluster |
Date: | 2020-05-22 18:54:34 |
Message-ID: | 4D7B766329AC4875AAC6FFADA988A9C4@dell2 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi!
>> ERROR: item order invariant violated for index "desktop_baas_liigid_idx"
>> DETAIL: Lower index tid=(3,15) (points to index tid=(16,4098)) higher index tid=(3,16) (points to index tid=(17,4098)) page
>> lsn=292/630C0CE8.
>> SQL state: XX002
>Uh huh ... and I'll bet the same test on the source server is just fine?
>I don't find it surprising in the least that different platforms have
>different ideas on fine points like how to sort a leading underscore.
>Those things just aren't that well standardized.
This column is not used for locale specific data.
Running
alter table desktop alter baas type char(8) collate ucs_basic
fixes the issue.
Is this fix reasonable ?
What other issues may occur ?
Can base backup created in windows using pg_basecakup used in Linux without such fix?
Andrus.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-05-22 19:37:59 | Re: query, probably needs window functions |
Previous Message | David G. Johnston | 2020-05-22 18:34:55 | Re: query, probably needs window functions |