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 1tDlch-0032kM-L5 for pgsql-general@arkaria.postgresql.org; Wed, 20 Nov 2024 14:24:03 +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 1tDlcf-006HTI-4M for pgsql-general@arkaria.postgresql.org; Wed, 20 Nov 2024 14:24:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tDlce-006HTA-NE for pgsql-general@lists.postgresql.org; Wed, 20 Nov 2024 14:24:00 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tDlcY-002w5z-Gr for pgsql-general@lists.postgresql.org; Wed, 20 Nov 2024 14:24:00 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e387ad7abdaso4983601276.0 for ; Wed, 20 Nov 2024 06:23:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uwalumni.com; s=google; t=1732112632; x=1732717432; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QbqU4w3DakweRdejaXuX8ZOPvD0TWcZ4wqDs07onm9Q=; b=J//tA+S6Avgwp5uHjNDFNEhnWqYDRKDpnfQlUUjL5Jf2owbMG/k4Xh1zET2LDeisYG 8tH6x8Ybqr1ad1MzXhwytNDInMUNA8CYwZ4j/4Hq2nJAYOB3mjFELZRC9kgS7kphwm19 tTos2Ph1Mvqk20p9TioXd6pcIiwl6ok1Q0bQE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732112632; x=1732717432; h=cc: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=QbqU4w3DakweRdejaXuX8ZOPvD0TWcZ4wqDs07onm9Q=; b=a2oaihXGCx30vvNI0a4AuPG3mLWibNrXhA/27wJNt+EXrHirxs+Zkt5U06BbrQmQOi oFcOcf4WL7dUbBUp3vd+xMCTgd0lHC+By8AGiWIVdPsJlYm0+1w89a6A60i7G4G/949M 1Sy3zDcIxlff5sUmIL8TqKxB4rGOpyKPlQo+6S26VMaZe9cADkLw8xRHJMu6Ovk9xYca xgvh0rHPbNXI4JpQH4K+BC5SYNR4bwBjcuyLfVpm/FPCcb/781z8MvUqZTXh8QZEIoLU F4hSx855jr6YHHBsnlJdlnb1PZ9nRjqZgYuobSUi6uUmL7AC7z/wAfjyzzuFCqEqmD+8 uM3A== X-Forwarded-Encrypted: i=1; AJvYcCU1xTfZ21qQsnNVGGKazn7tXxbgwy3Xdixk3mnsC0C4L6JfdAbS3UgWh1/BxZNYY6Q6ESGzQKo5jZHA/Rkp@lists.postgresql.org X-Gm-Message-State: AOJu0YwC66C0G+AVfsVEHCPNFMjI9t88LXbRyTsOhdK4szSbubT4gkNT fnVNCL9ZIIqwdfEUU1H6Zgcw6CGCG68IIxEnkWAT9Lzt5pO3nav4iL1JbdLWSL+d7kun8EnfYPx mEhqxEA9czjriwh8uZM1thwSFi3Evc/rs0rI9/g== X-Google-Smtp-Source: AGHT+IE3YeVPAVCg3BKUNjkZP2BKaBsTjiB/HGZxbsoL+EbzFmL8RYqtXn6x7EIksws6rOfQKHf+vDsNvJL5XhiTx2Y= X-Received: by 2002:a05:6902:70c:b0:e38:b2ce:987 with SMTP id 3f1490d57ef6-e38cb54be8cmr2581030276.3.1732112632523; Wed, 20 Nov 2024 06:23:52 -0800 (PST) MIME-Version: 1.0 References: <1fe9de96-6ebe-4e3a-9b15-ae8a11986664@aklaver.com> <11b5cfbd-cb44-4bc5-b74e-c6c682d9cfb9@aklaver.com> <1f9bc817-8a8d-4ff7-bf66-41a9e882da1a@aklaver.com> In-Reply-To: <1f9bc817-8a8d-4ff7-bf66-41a9e882da1a@aklaver.com> From: Catherine Frock Date: Wed, 20 Nov 2024 09:23:39 -0500 Message-ID: Subject: Re: Help with restoring database from old version of PostgreSQL To: Adrian Klaver Cc: Ron Johnson , "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000002c471b062758e6a9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002c471b062758e6a9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Adrian: Yes, db_2017 is the name I originally gave the database in the PostgreSQL 9.6 server. I can't remember if I used pg_dump or pg_dumpall. Ron: Okay, I think it finally worked! Thank you both for your help. -- Arden On Tue, Nov 19, 2024 at 6:00=E2=80=AFPM Adrian Klaver wrote: > On 11/19/24 14:13, Catherine Frock wrote: > > Do you know what versions of PG and pgAdmin4 I need? Also, I don't know > > where to get a different version of PG. > > > > You need to take a step back and take stock of where you started and > where you want to be. > > To that end answer the following: > > 1) What are the Postgres and PostGIS versions you started with? > > 2) What database or databases do you want to move forward? > > 3) Is there a hard requirement for what currently supported version of > Postgres you want to use? > > 4) What do you want to do with the new install? > > 5) What versions of Postgres, pgAdmin4 and PostGIS do you currently have > installed? > > 6) You are looking at jumping a minimum of 4 major Postgres versions up > to a maximum of 8 versions. You are also jumping some number of PostGIS > versions as well. In either case you should at some point go over the > release notes for each major version jump to see if anything is going to > cause issues. > > > -- > > Arden > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --0000000000002c471b062758e6a9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Adrian: Yes, db_2017 is the name I originally=C2= =A0gave the database in the PostgreSQL 9.6 server. I can't remember if = I used pg_dump or pg_dumpall.

Ron: Okay, I think it finally worked!<= br>
Thank you both for your help.

--
Arden
<= br>

On Tue, Nov 19, 2024 at 6:00=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
=
On 11/19/24 14:13, = Catherine Frock wrote:
> Do you know what versions of PG and pgAdmin4 I need? Also, I don't= know
> where to get a different version of PG.
>

You need to take a step back and take stock of where you started and
where you want to be.

To that end answer the following:

1) What are the Postgres and PostGIS versions you started with?

2) What database or databases do you want to move forward?

3) Is there a hard requirement for what currently supported version of
Postgres you want to use?

4) What do you want to do with the new install?

5) What versions of Postgres, pgAdmin4 and PostGIS do you currently have installed?

6) You are looking at jumping a minimum of 4 major Postgres versions up to a maximum of 8 versions. You are also jumping some number of PostGIS versions as well. In either case you should at some point go over the
release notes for each major version jump to see if anything is going to cause issues.

> --
> Arden
>


--
Adrian Klaver
adrian.klave= r@aklaver.com

--0000000000002c471b062758e6a9--