Re: Postgresql streaming replication - Mailing list pgsql-admin

From Prasanth
Subject Re: Postgresql streaming replication
Date
Msg-id b289a9c5-8e0c-09af-8aa9-7b8394e4dba5@pangburngroup.com
Whole thread Raw
In response to Re: Postgresql streaming replication  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: Postgresql streaming replication
List pgsql-admin
I ran few queries and the recent data seems to be there. Would this cause differences in sorting or are there bigger issues with this difference in glibc libraries?

Thanks,
Prasanth

On 5/28/24 9:55 AM, Scott Ribe wrote:
On May 28, 2024, at 8:50 AM, Prasanth <dbadmin@pangburngroup.com> wrote:

Hi,

We are running postgresql 16 on debian 12. I tried to create a hot standby on a different server that is running alma linux 9.  After doing the backbackup and starting the server seems like the replication is going fine. When I tried to login to the standby to run some queries got the below message. Postgresql is installed using rpm.

DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.34.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE database_name REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
Yep. Different versions of Linux changed collation rules in the glibc locale implementations. You will not be able to do streaming replication between those two Linux versions with those two builds of PostgreSQL. You will have to either:

- get Linux versions with same (or close enough) glibc versions

- figure out how to build PostgreSQL yourself with a compatible version





pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: Postgresql streaming replication
Next
From: Scott Ribe
Date:
Subject: Re: Postgresql streaming replication