From: Thomas Kellerer <shammat@gmx.net>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Regarding query on the postgresql upgrade
Date: Thu, 15 Oct 2020 13:24:30 +0200
Message-ID: <fd13570e-58ff-9be6-c9e7-339473deadea@gmx.net> (raw)
In-Reply-To: <CABUevEwhP-U08yDGuPN9fftDNNiuBkstj9cwWoF2GNSHm0XfXQ@mail.gmail.com>
References: <CAGeQtUsfuCkMxjYGqtnTyJm0o-rOe2OX4uwTSZ7BVE9cH+aXGQ@mail.gmail.com>
<8148c916-87ea-e36c-763e-ad7ed9311e34@gmx.net>
<CABUevEwhP-U08yDGuPN9fftDNNiuBkstj9cwWoF2GNSHm0XfXQ@mail.gmail.com>
Magnus Hagander schrieb am 15.10.2020 um 12:27:
> Ramesh Penuballi schrieb am 15.10.2020 um 10:27:
> > We are planning to upgrade the postgres version from 9.2.13 to
> > 9.4.25 by keeping the support version of Atlassian in mind.
> >
> > But to proceed the same in production, we have tried to run the
> > pgdump command to take the backup of all the databases and getting
> > the below error when we tried to take the dump of Eazybi database
> > which is not present on our stage environment.
>
> For a minor version upgrade you only need to install the new binaries and restart the Postgres service.
>
>
> 9.2 to 9.4 is not a minor upgrade though. It's a major upgrade, so
> either pg_dump/pg_restore or pg_upgrade will need to be used.
A shoot. For some reason I thought it was 9.4.13 to 9.4.25
Sorry for the noise.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Regarding query on the postgresql upgrade
In-Reply-To: <fd13570e-58ff-9be6-c9e7-339473deadea@gmx.net>
* 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