Re: Hot Standby setup - collation version mismatch - Mailing list pgsql-admin

From Ron Johnson
Subject Re: Hot Standby setup - collation version mismatch
Date
Msg-id CANzqJaDzgQsF_S17qSpcKGJ1vkzOJG1E6mRON26e4DAA2_9Lcg@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby setup - collation version mismatch  (Joe Conway <mail@joeconway.com>)
Responses Re: Hot Standby setup - collation version mismatch
List pgsql-admin
On Tue, Feb 25, 2025 at 2:17 PM Joe Conway <mail@joeconway.com> wrote:
On 2/25/25 12:47, Ron Johnson wrote:
> On Tue, Feb 25, 2025 at 12:43 PM Sbob wrote:

>     I have 2 aws ec2 nodes and I want to setup a hot standby.
>
>     The master is running amazon linux

>     The standby is running Alma 8

>     Once I run pg_basebackup I start the standby and get this:

>     WARNING:  database "postgres" has a collation version mismatch
>     DETAIL:  The database was created using collation version 2.34, but
>     the operating system provides version 2.28.
>     HINT:  Rebuild all objects in this database that use the default
>     collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION,
>     or build PostgreSQL with the right library version.

> One is RHEL 8, and the other is RHEL 9.  Never do that using streaming
> replication, for the very reason you're seeing:
>   WARNING:  database "postgres" has a collation version mismatch
>
> Use logical replication, or upgrade the hot standby server to Alma 9.

He actually said Amazon Linux (based on glibc version I would guess
AL2023) & Alma 8, but the point remains the same.

Isn't "_el9" in the package names a reference to RHEL9 compatibility?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-admin by date:

Previous
From: Joe Conway
Date:
Subject: Re: Hot Standby setup - collation version mismatch
Next
From: Joe Conway
Date:
Subject: Re: Hot Standby setup - collation version mismatch