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 1uPLfa-005hxg-R4 for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jun 2025 13:39:11 +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 1uPLfX-003849-O0 for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jun 2025 13:39:08 +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 1uPLfX-00382s-CB for pgsql-admin@lists.postgresql.org; Wed, 11 Jun 2025 13:39:08 +0000 Received: from mail-oo1-xc33.google.com ([2607:f8b0:4864:20::c33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uPLfW-001R8g-0w for pgsql-admin@postgresql.org; Wed, 11 Jun 2025 13:39:07 +0000 Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-605fda00c30so3789082eaf.1 for ; Wed, 11 Jun 2025 06:39:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1749649145; x=1750253945; darn=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=V4DtoYVJFIJF4Io3d3ZZFSIOIKbdjO/rZkRZfl10640=; b=K7MYdUB6T4lzRKhYBN0JPJ5y0AUN/cpiXLi9nUdEudW2C0GlGbA3H5IZICBID+MLhP lcPL4f777DCkJQS5GYu+DxXNyABUOGlAzm3ZUDwcrE2O3oeDKu8nKnQEQjNcSrsrLJDZ vbhp4/9N0YTbVSIgR4mMeasUYeQlAOvvu3RAcnG5gB74x8r/PHGoICau1Wg0mcd1vjJy f6gvaEY+EtOSs9UdrCM8ggi8vx/GjfYxGUQmjPmbGiYUZSyyGlRW/rcnmlkTezK7iiJU 9pDSiYWnUNyib8DOVGBODPOgyiZZ9mEYCG5AhECmbd/+71B+3a0xBZ4cPjr9GZYWTQ4u zfQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749649145; x=1750253945; 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=V4DtoYVJFIJF4Io3d3ZZFSIOIKbdjO/rZkRZfl10640=; b=Fxw4PQ2mCry+oVIV494JNvlUGqU45iagEGNLI8aXCofmWSDJL9pD7beklbHsuGeQ/x sKyZRcvZq7No4vTZ+R9AmEnywK4wqjAxhwff7o6KY+lcbJIqt19CfJhswQNwi7Gt/KbV +sWZTQoFpdJHg9Cf5X3g8eqxulsj7MR9W3fYV06UHN+5/Pd9I960T27M3yIND4shoNK2 fQTfcCAbk9YHGC4iNZ36Pw2eiX5aeeBflMSSFFXZVC4bZZBheYOYznJEBMNeq72+HLRE PRVGxbWzdeu38D//ihrHKuvOcWHG6dpCGhRLKYTnhRxL/AOV5OW7HzZA5rKSOwNiq6n+ lprw== X-Gm-Message-State: AOJu0YyI4HNgSaCIFaM0RRVVQ6aR97yModyaj1Tqau+Y0PTxYNISQNuL 9OmZUqsXmLdNE6jatNki5T8RqLaDToiDR7ukxzCtRTUcGyc4iIjLAWhFq3+qUnq9vTwdqABWTg9 2fWMI2ISZIbyGuFC7PlpIxK8sjucUb8TtBw== X-Gm-Gg: ASbGncufy4LPNKkIW2htKw4EodB4JID/abPHDyMRsp3nHaA9k9Lo75vgyHVApvVB7Ig oLQCdH4ku068hfQqfyR8b16Kf95JPe8qycpumafTdZlwwJdFcnefhAZ9zMXKONdT5rJCUc9gU6f NY++6msvlwVyrqHdg5Eqgeiap6PtFkxriF7M6xvbqkuSBoHQi7vxtkmq4= X-Google-Smtp-Source: AGHT+IHbWoaCYiS1ejSHwjJSnACu5kC+sW17uJk+G3Yqw0hBbwyniT+cGENCa2ksSJsswmMYFok0W7IBxbBgznCA4CA= X-Received: by 2002:a05:6870:6243:b0:2d4:e8fd:7ffb with SMTP id 586e51a60fabf-2ea96bb0f15mr1839676fac.1.1749649145212; Wed, 11 Jun 2025 06:39:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Wed, 11 Jun 2025 09:38:53 -0400 X-Gm-Features: AX0GCFtApDbkztgooLNhw3lUVNd88I36iW3DdIbf-7pvTn2cI-LBgtAXuEf3TPU Message-ID: Subject: Re: Upgrade from 12.22 to 16 To: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000c8344d06374bef6f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c8344d06374bef6f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 11, 2025 at 2:54=E2=80=AFAM Wasim Devale w= rote: > I mean to say that we do not want to do the in place upgrade > Why not? Using the default --copy option, there's minimal downtime, and the old database is still there in case you need to fall back, etc. > also the other option of taking dump and restoration of it. If I can have > any robust plan who all have worked on that then please suggest me. > > Thanks, > Wasim > > ---------- Forwarded message --------- > From: Laurenz Albe > Date: Wed, 11 Jun, 2025, 12:13=E2=80=AFpm > Subject: Re: Upgrade from 12.22 to 16 > To: Wasim Devale , Pgsql-admin < > pgsql-admin@lists.postgresql.org> > > > On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote: > > Please suggest me to upgrade postgresql: 400 GB data with minimal > downtime apart > > from in place upgrade. We have it on red hat 9. > > What do you mean with "apart from"? > > Yours, > Laurenz Albe > --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c8344d06374bef6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 11, 2025 at 2:54=E2=80=AFAM W= asim Devale <wasimd60@gmail.com> wrote:

I mean to say that we do not want to do the in place upgr= ade

Why not?=C2=A0 Using the default --cop= y option, there's minimal downtime, and the old database is still there= in case you need to fall back, etc.
=C2=A0

also the other option of taking dump and restoration of it. If I= can have any robust plan who all have worked on that then please suggest m= e.

Thanks,
Wasim


---------- Forwarded message -----= ----
From: Laurenz Albe<= /strong> <laurenz.albe@cybertec.at>
Date: Wed, 11 Jun, 2025, 12:13=E2=80=AFpm
Subject: Re: Upgrade fro= m 12.22 to 16
To: Wasim Devale <wasimd60@gmail.com>, Pgsql-adm= in <pgsql-admin@lists.postgresql.org>

=
On Wed, 2025-06-11 at 11:51 +0530, Wasim Devale wrote:
> Please suggest me to upgrade postgresql: 400 GB data with minimal down= time apart
> from in place upgrade. We have it on red hat 9.

What do you mean with "apart from"?

Yours,
Laurenz Albe


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