pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthias Apitz <guru@unixarea.de>
To: Christophe Pettus <xof@thebuild.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: update to 16.2
Date: Fri, 8 Mar 2024 11:00:52 +0100
Message-ID: <Zerh1Lr+o03EJmDm@pureos> (raw)
In-Reply-To: <B6D8F675-8BB7-4DD3-B325-C2C4F776C6D9@thebuild.com>
References: <ZerSFS6iNNGPyo0W@pureos>
	<B6D8F675-8BB7-4DD3-B325-C2C4F776C6D9@thebuild.com>

El día viernes, marzo 08, 2024 a las 12:56:16 -0800, Christophe Pettus escribió:

> 
> 
> > On Mar 8, 2024, at 00:53, Matthias Apitz <guru@unixarea.de> wrote:
> > It does not say definitely that for all other versions a dump/restore is
> > required.
> 
> You cannot just replace the binaries to upgrade from an earlier major version to 16.X.  The release notes use "a dump/restore (is/is not) required" to indicated whether you can just replace the binaries ("is not") and restart the server on the same database files.
> 

I know we can't just switch the binaries and restart the server. We're
compiling the PostgreSQL software by our own (even with some small
changes in the C-code) and deliver the full tree as

/usr/local/sisis-pap/pgsql-11.1 
/usr/local/sisis-pap/pgsql-14.1 
/usr/local/sisis-pap/pgsql-15.1 
...

Also the migration path for customers is described and based on
pg_dumpall, setup a new cluster fromm the above new version and load the
dump with the new psql command into. The other option (pg_upgrade) we
never used.

	matthias

-- 
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

I am not at war with Russia.  Я не воюю с Россией.
Ich bin nicht im Krieg mit Russland.





view thread (7+ messages)  latest in thread

Message-ID: <Zerh1Lr+o03EJmDm@pureos>
Permalink:  ../Zerh1Lr+o03EJmDm@pureos/
Also on:    postgresql.org/message-id/Zerh1Lr+o03EJmDm@pureos

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: guru@unixarea.de, xof@thebuild.com
  Subject: Re: update to 16.2
  In-Reply-To: <Zerh1Lr+o03EJmDm@pureos>
  References: <ZerSFS6iNNGPyo0W@pureos> <B6D8F675-8BB7-4DD3-B325-C2C4F776C6D9@thebuild.com> <Zerh1Lr+o03EJmDm@pureos>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox