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 1ts2XI-00DhWd-8D for pgsql-general@arkaria.postgresql.org; Tue, 11 Mar 2025 16:32: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 1ts2XG-002Kb7-Va for pgsql-general@arkaria.postgresql.org; Tue, 11 Mar 2025 16:32:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ts2XG-002KSu-LW for pgsql-general@lists.postgresql.org; Tue, 11 Mar 2025 16:32:54 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ts2XD-002GAh-2m for pgsql-general@lists.postgresql.org; Tue, 11 Mar 2025 16:32:52 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3f94b7bd907so992870b6e.2 for ; Tue, 11 Mar 2025 09:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741710771; x=1742315571; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=zWtOVFPFv1/NPhLJ9wDKLXlXXsLvvlQ06DMOetlVxW0=; b=FN3Bd+jz1PHb9MRuH+1Ky0/JRGH5q/6FdrJXPz68EwEDUtGU2PijWf+5siTLZAQdSe ad6w+xdv7T+x+NSZZFWO+/h2ncGkoUzGaJxVUzbEXFuSkQtjs0Paxv+HyQrRWDB8ZXrV lOcjDTNTX7SYpaod6ov3AIVzD/42LXYaGq4kSodO4Ap1iYHRozl3JnKF6dT2puWIeFbe blwgYZ3Re/xfy8D+wHok+f8RXb1zWEOqG0Ol7oVTINBjL1s+7aB7//FJLbK4qbAI5Ham cADVMED7V2KWB0z4Z6r9F5rDeX4VlmaDHWIfmghfb8mnS646A/GSdTSn7OIv61dwe1mR vnAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741710771; x=1742315571; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zWtOVFPFv1/NPhLJ9wDKLXlXXsLvvlQ06DMOetlVxW0=; b=ISN65aYwGUGbMZeBj99JUd8t2R/j1TkH8J0ZK6zmHjr0qGY+tDk1h5Oz1WGjjwiwhR OOUNFUf+Hg9gB8zHlA8VkC3DwuteJQYMx8ZsTSay2S9Oiu9EIWt1K5Krt5NpZWj06bOW LrrxFuXkRBwfV5pNM13iy9kzopaAPCdekg24w28ZjPbooRWEnoOiJcE8XtPWWo4rFdK8 +Cupwa/9u+H4ZhXLlV7yheL03IERW6Z/ybTirZbhOdoDzXL8+WFFX/9vT3R+cOacoi/4 1Tdu2xPlac/bkZd7JpeI6Yufv365G3NYItVZZUkMisT4PaurDsxDH0wJiZ9PLIQVVE3j +kDw== X-Gm-Message-State: AOJu0YxxrFCjlq8wZN8OixpIoifs/58nCeld1B48Mq6jm2l2whlNJ2sx vour8HjCESCFf0+bNIfFYc1cIKC+wPeQsUYTtho5XlVNARFttKYZJ6EvZLhXGbKv6EnoF/2YKfc faIkTLxmyflmP2bjzABxbrDm3Dh1OeA== X-Gm-Gg: ASbGncsqTbhp8c5nf5QtMy61yEu0yduKv3uBoBTmKtTVp1E0Q3GwU8p6ZBoyjzPPfCp YFthM5qLVxZ1Auwkh0QE6Cc+S99jIIFXOGLN91Lnko3JG+fQOiOC/2f7Twm16O2qpJkJswV2M0D 2b2ZNUxXOy2hsLQ6zgnpLNdZT4/UnWEQYgNPdZUxYsleeElgEYJSJSvWr5wg6A X-Google-Smtp-Source: AGHT+IGa6W6Q6enY5NBXRJksNQ2GpGTaDTIqdLCCrbqRv/SQY9vN/X6Vv/E/FFB4Uz0gU7FxCWEBbFhb47nXmwmaNgA= X-Received: by 2002:a05:6808:1242:b0:3f8:150b:f571 with SMTP id 5614622812f47-3f8150bf837mr5604251b6e.21.1741710770727; Tue, 11 Mar 2025 09:32:50 -0700 (PDT) MIME-Version: 1.0 References: <6E6059F6-E5A1-4A8D-8A5E-A41B921BBE67@gmail.com> In-Reply-To: <6E6059F6-E5A1-4A8D-8A5E-A41B921BBE67@gmail.com> From: Ron Johnson Date: Tue, 11 Mar 2025 12:32:39 -0400 X-Gm-Features: AQ5f1JrxRUfegF6Xic6j7Eeyz6U4mPOAOo8ibqXt0pQImV6mSLMcK5Rmqpu0OeQ Message-ID: Subject: Re: Moving from Linux to Linux? To: Pgsql-General List Content-Type: multipart/alternative; boundary="000000000000ca7f4a063013a384" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ca7f4a063013a384 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Mar 11, 2025 at 12:23=E2=80=AFPM Paul Foerster wrote: > Hi, > > we are considering changing the PostgreSQL platform from SUSE SLE to Red > Hat. To keep service interruptions as short as possible, the idea is to s= et > up a streaming replication from the SUSE server to be replaced to a > temporary Red Hat server and then replace that SUSE server with the newly > setup Red Hat server. > > My idea is to set up a streaming replication for this. But this of course > only works if the data files would be binary compatible. > > So, I wonder, if this is possible. We have a lot of databases, some of > them need to be highly available and some are large too. > > Are there any obstacles that definitely make that a no-go? Do I risk > corruption? It's both Linux, just a different distribution. > The same version of PG will be on both, right? What version of RHEL? What version of SLES? Those questions are proxy for: what version of glibc on each system? If they're the same, and you use libc for collation, then you're (probably) good to go. If they're different, then you should use logical replication. Otherwise, string collation mismatch could bite you on any indices on text fields. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000ca7f4a063013a384 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Mar 11, 2025 at 12:23=E2=80=AFPM = Paul Foerster <paul.foerster@= gmail.com> wrote:
Hi,

we are considering changing the PostgreSQL platform from SUSE SLE to Red Ha= t. To keep service interruptions as short as possible, the idea is to set u= p a streaming replication from the SUSE server to be replaced to a temporar= y Red Hat server and then replace that SUSE server with the newly setup Red= Hat server.

My idea is to set up a streaming replication for this. But this of course o= nly works if the data files would be binary compatible.

So, I wonder, if this is possible. We have a lot of databases, some of them= need to be highly available and some are large too.

Are there any obstacles that definitely make that a no-go? Do I risk corrup= tion? It's both Linux, just a different distribution.
<= div>
The same version of PG will be on both, right?

What version of RHEL?=C2=A0 = What version of SLES?=C2=A0 Those questions are proxy for: what version of = glibc on each system?

If they're=C2=A0the same= , and you use libc for collation, then you're (probably) good to go.

If they're different, then you should use logica= l replication.=C2=A0 Otherwise, string collation mismatch could bite you on= any indices on text fields.

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