AW: V16 to V18 Upgrade with pg_dumpall -- Question - Mailing list pgsql-novice

From Subramanian,Ramachandran
Subject AW: V16 to V18 Upgrade with pg_dumpall -- Question
Date
Msg-id 320d522ca4854a159a6f6cddbb383db9@alte-leipziger.de
Whole thread
In response to Re: V16 to V18 Upgrade with pg_dumpall -- Question  (Justin <zzzzz.graf@gmail.com>)
List pgsql-novice

Hello all,

 

I worked with our Linux team and got them to install an image that allows in place upgrade. I tested it and it works.

 

Thank you all for all your inputs.

 

LG


Ram

 

Freundliche Grüße

i. A. Ramachandran Subramanian

Zentralbereich Informationstechnologie

Alte Leipziger Lebensversicherung a. G.

Hallesche Krankenversicherung a. G.

______________________

ALH Gruppe
Alte Leipziger-Platz 1, 61440 Oberursel
Tel: +49 (6171) 66-4882
Fax: +49 (6171) 66-800-4882
E-Mail: ramachandran.subramanian@alte-leipziger.de
www.alte-leipziger.de
www.hallesche.de

Alte Leipziger Lebensversicherung a. G., Alte Leipziger-Platz 1, 61440 Oberursel

Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Robert Gladis, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Udo Wilcsek

Sitz Oberursel (Taunus) · Rechtsform VVaG · Amtsgericht Bad Homburg v. d. H. HRB 1583 · USt.-IdNr. DE 114106814

Hallesche Krankenversicherung a. G., Löffelstraße 34-38, 70597 Stuttgart

Vors. des Aufsichtsrats: Dr. Walter Botermann · Vorstand: Christoph Bohn (Vors.), Dr. Jürgen Bierbaum (stv. Vors.), Robert Gladis, Dr. Jochen Kriegmeier, Alexander Mayer, Christian Pape, Udo Wilcsek

Sitz Stuttgart · Rechtsform VVaG · Amtsgericht Stuttgart HRB 2686 · USt.-IdNr. DE 147802285

Beiträge zu privaten Kranken- und Pflegekrankenversicherungen unterliegen nicht der Versicherungsteuer (§ 4 (1) Nr. 5 b VersStG) · Versicherungsleistungen sowie Umsätze aus Versicherungsvertreter-/Maklertätigkeiten sind umsatzsteuerfrei

Pflichtangaben der ALH Gruppe gemäß § 35a GmbHG bzw. § 80 AktG

Von: Justin <zzzzz.graf@gmail.com>
Gesendet: Montag, 21. September 2026 15:39
An: David G. Johnston <david.g.johnston@gmail.com>
Cc: Subramanian,Ramachandran IT-md-db <ramachandran.subramanian@alte-leipziger.de>; pgsql-novice@lists.postgresql.org
Betreff: Re: V16 to V18 Upgrade with pg_dumpall -- Question

 

I do not think this accurate unless something has changed.  

 

Redhat packages install the binaries then leave all the configuration up to admin/DBA.  Data directory, initialize the database etc...  

 

If the packages detect and prevent installation of multiple pg versions  I would say switch to the redhat pg community package

 

On Mon, Sep 21, 2026, 8:13 AM David G. Johnston <david.g.johnston@gmail.com> wrote:

On Monday, September 21, 2026, Subramanian,Ramachandran <ramachandran.subramanian@alte-leipziger.de> wrote:

Our Linux Admin tells us that the image he downloads is from REDHAT and not from POSTGRES and it allows only one version of Postgres to be installed at any given time.

 

Either this is true and you can’t do what you want below, or it’s false and you can.

 

But yeah, usually either you install two versions one the same machine at the same time e or you install one version on each of two machines at the same time.   Both these tend to minimize downtime and risk.  There is a bit of complexity to do either.

 

David J.

 

pgsql-novice by date:

Previous
From: Justin
Date:
Subject: Re: V16 to V18 Upgrade with pg_dumpall -- Question