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 1tIHPJ-00DNc3-Ap for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 01:08:53 +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 1tIHPG-005Ssd-Qe for pgsql-general@arkaria.postgresql.org; Tue, 03 Dec 2024 01:08:52 +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 1tIHPG-005SsV-FT for pgsql-general@lists.postgresql.org; Tue, 03 Dec 2024 01:08:51 +0000 Received: from mail.hjp.at ([212.17.106.138] helo=rorschach.hjp.at) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tIHPD-000k1F-VG for pgsql-general@lists.postgresql.org; Tue, 03 Dec 2024 01:08:50 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id BF816AD6F; Tue, 3 Dec 2024 02:08:44 +0100 (CET) Date: Tue, 3 Dec 2024 02:08:44 +0100 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X Message-ID: <20241203010844.3cqe6ds6ainih4b3@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org References: <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <1760813407.5166251.1733182880136@mail.yahoo.com> <32763ce5-76e6-454d-bd64-53db8b2b9af6@aklaver.com> <54665410.4461273.1733183579920@mail.yahoo.com> <78f9dd08-4d28-4ed8-897e-b94889dbfd46@aklaver.com> <2102730591.3974293.1733185515380@mail.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="jflpbj6mw77jn2pm" Content-Disposition: inline In-Reply-To: <2102730591.3974293.1733185515380@mail.yahoo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --jflpbj6mw77jn2pm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2024-12-03 00:25:15 +0000, Bharani SV-forum wrote: > qsn1: What is the size of database(s) you are dealing with? > ans1: roughly 25 GB (maximum size) >=20 > qsn2 : What sort of downtime can you afford? > ans2: can be maximum 30 mins or so That does seem sufficient time to dump/restore a 25 GB database, so that's what I'd try first. It's simple and you can easily test it without disruption. hp --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --jflpbj6mw77jn2pm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmdOWhYACgkQ8g5IURL+ KF0MdA//ZPe+2lhymoDgR+AwcpmaP7KD+LxLKjSZRupiKN5BaXSc32XRXDsGdWVT 1j6R+wRrBE5yCmuR5ybFISMydSUgoQCIr7q0bn8fZenqpGHS9qykV0cgwCNeTnQP SjRUaAqXbPmVQ7qkkPXcZmMikOZ/a9ZAYRlc6XAnd/kkun+iT9Ter+JvC9PxdO4d W8wTBkM4m4Zq/gPfJDuR9ymg/TaGsBsr5MjYdqHqpvYAKGgjlabHRlC+y2u6wlG8 3UGzM8B5DzXC4PIUUBfzdAKWJa6sv3kgdP7SBQvJ5dmMkQVWrng6p/WVR6LRnTEi T2iJC9L9SzX5LBs3J4rl3FsVQBajKqI1gbT0+3e2swGZl1uStOAMCn2XIvTEZeXW y2FxWJkd2qWXzrvoK+LEbPjA9YTO4B6L0i6DNFGVJLN6mgvq+6byKI2LiF/Aq5HA fHk1h6ws/F2pRajg3Y/u0Qsk242CY3/7s0iED+BCA8Ak+OoITD+UpdLNixMkmnLn oJTXOwOecsc1FRgvAN11j8By0mWKxz4RL5CZfwAfb/lUmBuTAJqk1mGCmTKn5koX KmxaP0SqXiEiDXsYdPZoHH7i2jTwv+8fbDzKR0MXBWgfWyO64nlWTTezcxIqN6Nw hi54hVH2CAPJi2uh3ohIeinl0nW7j+bHfanbehx/ZHiBIgn3g5U= =k2cO -----END PGP SIGNATURE----- --jflpbj6mw77jn2pm--