From: | Mohammed Afsar <vmdapsar(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Reindex doesn’t not working replica nodes |
Date: | 2024-08-16 13:48:44 |
Message-ID: | CA+6HdusYzHKxoUPHGrf6wVjBMe3Luo6S5iy+j9Dte+qija-0_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Got it thanks for the deep dive explanation.Scott 👍🏻
And parallel we got below error also included OS incompatibility?
postgres[265938]: segfault at 18 ip 00000000004cf11b
Regards,
Mohammed Afsar
On Fri, 16 Aug 2024 at 6:49 PM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Aug 16, 2024, at 7:08 AM, Mohammed Afsar <vmdapsar(at)gmail(dot)com> wrote:
> >
> > We are using streaming replications but still reindex is not working
> source db has 11.15replica has 11.11 PostgreSQL version.
>
> This is not your problem.
>
> As you understand, I think, with streaming replication all files,
> including indexes, are exactly duplicated on the replica. If the OS on the
> two sides have different glibc versions which have different collations,
> then the index structure of the primary will be a corrupted index on the
> replica. You have to fix your OS version incompatibility, or move to a
> version of postgres which can use ICU collations and make sure that library
> is compatible on both sides.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dirk Krautschick | 2024-08-19 15:26:12 | ERROR: multixact "members" limit exceeded |
Previous Message | Scott Ribe | 2024-08-16 13:19:04 | Re: Reindex doesn’t not working replica nodes |