Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qDq8A-0008WT-0D for pgsql-admin@arkaria.postgresql.org; Mon, 26 Jun 2023 17:36:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qDq87-0004aV-0L for pgsql-admin@arkaria.postgresql.org; Mon, 26 Jun 2023 17:35:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qDq86-0004aK-Fe for pgsql-admin@lists.postgresql.org; Mon, 26 Jun 2023 17:35:58 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qDq83-000ce6-5a for pgsql-admin@lists.postgresql.org; Mon, 26 Jun 2023 17:35:57 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-2b6a675743dso12608101fa.2 for ; Mon, 26 Jun 2023 10:35:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20221208.gappssmtp.com; s=20221208; t=1687800953; x=1690392953; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=zt1Me4eB5eXJlyYgB937QDze2djAvEYNkmbY/9dv2TM=; b=ZMWEJz9zwpjXnJ1EBVkslQzPc1fFrrXGow3iDz0L4g5McATLNNLW9dpKuZRlxXbOOj rEcS6cSx5ogiuvYXix0kSuwFmZbtvxPwJbs/sDr2zJLbv1ducfF2Slxu7sdH4Nw54DzU eBcvMy3auxES1DOYww1c12z4g996kqRx2OFG0RFARP5O3DX4Zz9PW0hzq4l5Ep2vT9Nt jVXvJRwAo1TIgWyqOgPLZ0KvBDkJGGIMsx/z8komJ4bpG1MJgnNVBCQ4UhhB+GPhb/aR wi13wavVA2qgZinXhkb9CX4SXc4grSMLwOBkuTPzeG/viH0LeR2sCWsTvIzYOL9jXSU6 HRAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687800953; x=1690392953; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=zt1Me4eB5eXJlyYgB937QDze2djAvEYNkmbY/9dv2TM=; b=KthVV5gS2d+KARr7ev0y9kQi+cMTzLzXFr1CTQmldiU+j3/1soNJTRhqREeL8mC3UY P6/xLlBbfBhRKNrhVoMWE4RTPZb0aA7jj/hgXf6F9kOzuWaGpHRmpwicXLNcavFFUfov 5PRi9D1BJ/4deWFcggqKX25csWBMiGWv7jga/EN4IuO/SZT67kydGP0x9wZ00xWf+BcW tM90FE4fFCLaqQDnMv+/C94VIv2KY2F6jmpUXIxhUVxw0RHAtfT5nClmtpu1aTR/DM30 j8IwF3SbNMxF6XhCAf+HjjqVKleUVLkccPGpTJ2hWAT1UlqeoFb5VOYTO70zCAdsljoy qQRg== X-Gm-Message-State: AC+VfDzxWKGsnJp/A0BwBX1zj37hzR296TomRWvVjg6DSYGPBMdk34n6 VZLjBina79/abl7lqo0Vq4Q1B6iCkqzezphVC/k= X-Google-Smtp-Source: ACHHUZ5wlOMR2+2Y04hwSPkS4RVTyYbAGmgZMKCLfGlVE8rLugqq4PObq7EtL2rofyHSXjyKSQxrjw== X-Received: by 2002:a2e:b042:0:b0:2b5:8102:1843 with SMTP id d2-20020a2eb042000000b002b581021843mr14864282ljl.18.1687800952940; Mon, 26 Jun 2023 10:35:52 -0700 (PDT) Received: from localhost.localdomain ([213.33.70.35]) by smtp.gmail.com with ESMTPSA id rn19-20020a170906d93300b0098822e05eddsm3455982ejb.100.2023.06.26.10.35.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Jun 2023 10:35:52 -0700 (PDT) Message-ID: Subject: Re: Linux in-place upgrade From: Laurenz Albe To: Murthy Nunna , "pgsql-admin@lists.postgresql.org" Date: Mon, 26 Jun 2023 19:35:45 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, 2023-06-26 at 17:13 +0000, Murthy Nunna wrote: > We are planning an in-place upgrade of Linux level from RHEL 7 to RHEL 8 = or RHEL 9. > We have several PG clusters running on this server using different versio= ns of postgres (pg12, pg13 and pg14). > =C2=A0 > We have couple of plans: > =C2=A0 > =C2=A0=C2=A0=C2=A01. Shutdown clusters, unmount disks that contain postgr= es data and wals, upgrade Linux, > remount postgres disks and restart postgres clusters > =C2=A0=C2=A0=C2=A02. Same as above but reinstall postgres (pg12, pg13 and= pg14) before restarting postgres clusters > =C2=A0 > Questions: > =C2=A0=C2=A0=C2=A01. Will 1 or 2 or both above work? > =C2=A0=C2=A0=C2=A02. Is there any official documentation above OS upgrade= s? The documentation is here: https://www.postgresql.org/docs/current/upgrading.html It depends on how you installed PostgreSQL. If you used binary packages, O= ption 1 should work fine. Don't forget to reindex all indexes on strings! Yours, Laurenz Albe