Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sByAB-002MJL-Ix for pgsql-admin@arkaria.postgresql.org; Tue, 28 May 2024 14:50:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sByAA-009qLN-IH for pgsql-admin@arkaria.postgresql.org; Tue, 28 May 2024 14:50:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sByAA-009qLE-6f for pgsql-admin@lists.postgresql.org; Tue, 28 May 2024 14:50:54 +0000 Received: from mail.nqadmin.com ([12.230.133.169]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sByA6-001BlA-3t for pgsql-admin@postgresql.org; Tue, 28 May 2024 14:50:52 +0000 Received: from mail.nqadmin.com (localhost [127.0.0.1]) by mail.nqadmin.com (8.14.7/8.14.7) with ESMTP id 44SEol1V028961 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 28 May 2024 09:50:47 -0500 Received: (from root@localhost) by mail.nqadmin.com (8.14.7/8.14.7/Submit) id 44SEolL1028960 for pgsql-admin@postgresql.org; Tue, 28 May 2024 09:50:47 -0500 Received: from [192.168.0.234] (ppasala.nqadmin.com [192.168.0.234]) (TLSv1/SSLv3 AES128-GCM-SHA256 128/128) by mail.nqadmin.com with SMTP id xetv5xrjxtkt73kiv2sriee94n; for pgsql-admin@postgresql.org; Tue, 28 May 2024 09:50:47 -0500 (CDT) (envelope-from dbadmin@pangburngroup.com) Content-Type: multipart/alternative; boundary="------------3tiJqio1WGocK3KztUMXV410" Message-ID: <06ab2de0-86d6-426e-4a18-17e0b25553ef@pangburngroup.com> Date: Tue, 28 May 2024 09:50:47 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Content-Language: en-US To: pgsql-admin@postgresql.org Reply-To: dbadmin@pangburngroup.com From: Prasanth Subject: Postgresql streaming replication X-Secure-Client-Email: No List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------3tiJqio1WGocK3KztUMXV410 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. Thanks, Prasanth --------------3tiJqio1WGocK3KztUMXV410 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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.


Thanks,
Prasanth
--------------3tiJqio1WGocK3KztUMXV410--