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 1riVzC-00Ha7S-OK for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 08:53:51 +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 1riVzA-00BFO9-CA for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 08:53:48 +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 1riVzA-00BFO1-1b for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 08:53:48 +0000 Received: from ms-10.1blu.de ([178.254.4.101]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1riVz6-003RyE-7P for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 08:53:47 +0000 Received: from [212.222.85.114] (helo=pureos) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1riVz4-0052lt-EL; Fri, 08 Mar 2024 09:53:42 +0100 Date: Fri, 8 Mar 2024 09:53:41 +0100 From: Matthias Apitz To: pgsql-general@lists.postgresql.org Subject: update to 16.2 Message-ID: Reply-To: Matthias Apitz MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 14.0-CURRENT 1400094 (amd64) X-message-flag: Mails in HTML will not be read! Send only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 212.222.85.114 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, We plan to update our customers on SuSE Linux from 11.4, 13.1, 14.1 and 15.1 to 16.2. Do I understand the release notes correct that for this the way is only dump/restore? The release notes say: https://www.postgresql.org/docs/release/16.2/ ... A dump/restore is not required for those running 16.X. ... It does not say definitely that for all other versions a dump/restore is required. We could even unload in the databases the ~400 tables to COPY format, re-create the tables in a new 16.2 server and load the ~400 files (all this relatively easy per scripts we created to migrate from Sybase and Oracle to PostgreSQL). But I think, producing the dump with the old version, setup new cluster and load the dump with the 16.2 sql command will work. Any comments? 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.