pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgresql community edition upgrade
8+ messages / 5 participants
[nested] [flat]
* Postgresql community edition upgrade
@ 2022-10-12 13:43 Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
0 siblings, 1 reply; 8+ messages in thread
From: Ebin Jozer @ 2022-10-12 13:43 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi all,
Can we upgrade the postgresql community edition version from 11 to 14
directly??
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
@ 2022-10-12 13:54 ` Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Holger Jakobs @ 2022-10-12 13:54 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Am 12.10.22 um 15:43 schrieb Ebin Jozer:
> Hi all,
> Can we upgrade the postgresql community edition version from 11 to 14
> directly??
Yes, all versions from 8.4 can be upgraded to the latest version directly.
--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
Attachments:
OpenPGP_signature (application/pgp-signature, 202B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
@ 2022-10-12 17:18 ` Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 17:28 ` Re: Postgresql community edition upgrade Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:21 ` Re: Postgresql community edition upgrade Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 2 replies; 8+ messages in thread
From: Ebin Jozer @ 2022-10-12 17:18 UTC (permalink / raw)
To: Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org
Thanks holger.
How to find it??
And
What would be the rollback step in case the upgrade failed while using
pg_upgrade??
On Wed, 12 Oct, 2022, 7:24 pm Holger Jakobs, <holger@jakobs.com> wrote:
> Am 12.10.22 um 15:43 schrieb Ebin Jozer:
> > Hi all,
> > Can we upgrade the postgresql community edition version from 11 to 14
> > directly??
>
>
> Yes, all versions from 8.4 can be upgraded to the latest version directly.
>
>
>
> --
> Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
@ 2022-10-12 17:28 ` Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:38 ` Re: Postgresql community edition upgrade Paul Smith <paul@pscs.co.uk>
1 sibling, 1 reply; 8+ messages in thread
From: Scott Ribe @ 2022-10-12 17:28 UTC (permalink / raw)
To: Ebin Jozer <ebinjozer@gmail.com>; +Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
> On Oct 12, 2022, at 11:18 AM, Ebin Jozer <ebinjozer@gmail.com> wrote:
>
> What would be the rollback step in case the upgrade failed while using pg_upgrade??
- pg_upgrade does pretty extensive pre-flight checks before proceeding
- it does not modify original files, but copies (& modifies the copied catalog files as needed)
(I think even if you use link mode, it doesn't modify original catalog files, so you can start the old one until you have started the new one. I'd look for more info from someone more knowledgeable about this exact process.)
I've personally never seen a problem once the pre-flight passes and it proceeds.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 17:28 ` Re: Postgresql community edition upgrade Scott Ribe <scott_ribe@elevated-dev.com>
@ 2022-10-12 20:38 ` Paul Smith <paul@pscs.co.uk>
2022-10-13 09:42 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Paul Smith @ 2022-10-12 20:38 UTC (permalink / raw)
To: Scott Ribe <scott_ribe@elevated-dev.com>; Ebin Jozer <ebinjozer@gmail.com>; +Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
On 12 October 2022 18:29:12 Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> (I think even if you use link mode, it doesn't modify original catalog
> files, so you can start the old one until you have started the new one. I'd
> look for more info from someone more knowledgeable about this exact process.)
Correct. I've had it go wrong with link mode. As long as you don't start
the new cluster, the old one still works absolutely fine with a minor
(documented) step.
IIRC, the data files (in /data/base) are linked (and unchanged by the
process). The control files, transaction logs, etc aren't, but the old
control files are "disabled" to prevent accidental starting of the old
cluster (it's easy to re-enable it)
See (17) of the Usage notes
https://www.postgresql.org/docs/current/pgupgrade.html
Paul
--
Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53
Sign up for news & updates at http://www.pscs.co.uk/go/subscribe
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 17:28 ` Re: Postgresql community edition upgrade Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:38 ` Re: Postgresql community edition upgrade Paul Smith <paul@pscs.co.uk>
@ 2022-10-13 09:42 ` Ebin Jozer <ebinjozer@gmail.com>
2022-10-13 12:51 ` Re: Postgresql community edition upgrade Scott Ribe <scott_ribe@elevated-dev.com>
0 siblings, 1 reply; 8+ messages in thread
From: Ebin Jozer @ 2022-10-13 09:42 UTC (permalink / raw)
To: Paul Smith <paul@pscs.co.uk>; +Cc: Scott Ribe <scott_ribe@elevated-dev.com>; pgsql-admin <pgsql-admin@lists.postgresql.org>
Hi thanks for the response so far.
We have master and slave environment. So for upgrade we have upgrade first
in slave and then in master environment. Please confirm
On Thu, 13 Oct, 2022, 2:13 am Paul Smith, <paul@pscs.co.uk> wrote:
>
>
> On 12 October 2022 18:29:12 Scott Ribe <scott_ribe@elevated-dev.com>
> wrote:
>
>> (I think even if you use link mode, it doesn't modify original catalog
>> files, so you can start the old one until you have started the new one. I'd
>> look for more info from someone more knowledgeable about this exact
>> process.)
>>
>
> Correct. I've had it go wrong with link mode. As long as you don't start
> the new cluster, the old one still works absolutely fine with a minor
> (documented) step.
>
> IIRC, the data files (in /data/base) are linked (and unchanged by the
> process). The control files, transaction logs, etc aren't, but the old
> control files are "disabled" to prevent accidental starting of the old
> cluster (it's easy to re-enable it)
>
> See (17) of the Usage notes
>
> https://www.postgresql.org/docs/current/pgupgrade.html
>
> Paul
>
>
> --
>
> Paul Smith Computer Services
> Tel: 01484 855800
> Vat No: GB 685 6987 53
>
> Sign up for news & updates <http://www.pscs.co.uk/go/subscribe;
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 17:28 ` Re: Postgresql community edition upgrade Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:38 ` Re: Postgresql community edition upgrade Paul Smith <paul@pscs.co.uk>
2022-10-13 09:42 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
@ 2022-10-13 12:51 ` Scott Ribe <scott_ribe@elevated-dev.com>
0 siblings, 0 replies; 8+ messages in thread
From: Scott Ribe @ 2022-10-13 12:51 UTC (permalink / raw)
To: Ebin Jozer <ebinjozer@gmail.com>; +Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
> On Oct 13, 2022, at 3:42 AM, Ebin Jozer <ebinjozer@gmail.com> wrote:
>
> We have master and slave environment. So for upgrade we have upgrade first in slave and then in master environment. Please confirm
Depends on your HA requirements.
Easiest: shut down primary and all db access, upgrade one, bring it back up as primary, upgrade other and bring it back online as replica.
Harder: use a replication scheme that works across versions (publish/subscribe, pglogical, londiste, bucardo) so that you can bring up a new replica on the new version, switch over to it with minimal downtime (just enough to make sure changes from master have been replicated), then turn the former primary into a new replica.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Postgresql community edition upgrade
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Re: Postgresql community edition upgrade Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Re: Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
@ 2022-10-12 20:21 ` Laurenz Albe <laurenz.albe@cybertec.at>
1 sibling, 0 replies; 8+ messages in thread
From: Laurenz Albe @ 2022-10-12 20:21 UTC (permalink / raw)
To: Ebin Jozer <ebinjozer@gmail.com>; Holger Jakobs <holger@jakobs.com>; +Cc: pgsql-admin@lists.postgresql.org
On Wed, 2022-10-12 at 22:48 +0530, Ebin Jozer wrote:
> What would be the rollback step in case the upgrade failed while using pg_upgrade??
If you don't use --link, the old cluster will still be there and can be used.
If you use --link, restore your backup.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2022-10-13 12:51 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-10-12 13:43 Postgresql community edition upgrade Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 13:54 ` Holger Jakobs <holger@jakobs.com>
2022-10-12 17:18 ` Ebin Jozer <ebinjozer@gmail.com>
2022-10-12 17:28 ` Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:38 ` Paul Smith <paul@pscs.co.uk>
2022-10-13 09:42 ` Ebin Jozer <ebinjozer@gmail.com>
2022-10-13 12:51 ` Scott Ribe <scott_ribe@elevated-dev.com>
2022-10-12 20:21 ` Laurenz Albe <laurenz.albe@cybertec.at>
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