Re: upgrade from 7.3.1 to 7.3.2

Started by Chantal Ackermannabout 23 years ago6 messagesgeneral
Jump to latest
#1Chantal Ackermann
chantal.ackermann@biomax.de

hello,

I would like to upgrade from 7.3.1 to 7.3.2 without loading the dump
data into the new database (this would take quite a while). I'd prefer a
faster way. pg_upgrade seems to be the way to go, but it is calling

pg_dumpall -s

though the -s option does not exist in pg_dumpall - neither in 7.3.1 nor
in 7.3.1. (how) is this supposed to work?

if pg_upgrade cannot be used - is there another way to transfer the data
to the new version without loading the dump?

thank you
Chantal

#2Ian Harding
ianh@tpchd.org
In reply to: Chantal Ackermann (#1)

I don't think you need to dump for a minor number upgrade.

Chantal Ackermann <chantal.ackermann@biomax.de> 02/10/03 08:51AM >>>

hello,

I would like to upgrade from 7.3.1 to 7.3.2 without loading the dump
data into the new database (this would take quite a while). I'd prefer a
faster way. pg_upgrade seems to be the way to go, but it is calling

pg_dumpall -s

though the -s option does not exist in pg_dumpall - neither in 7.3.1 nor
in 7.3.1. (how) is this supposed to work?

if pg_upgrade cannot be used - is there another way to transfer the data
to the new version without loading the dump?

thank you
Chantal

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#3Neil Conway
neilc@samurai.com
In reply to: Chantal Ackermann (#1)

On Mon, 2003-02-10 at 11:51, Chantal Ackermann wrote:

I would like to upgrade from 7.3.1 to 7.3.2 without loading the dump
data into the new database (this would take quite a while).

Read the release notes ("HISTORY"), which say:

Migration to version 7.3.2

A dump/restore is *not* required for those running 7.3.*.

Cheers,

Neil
--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC

#4Chantal Ackermann
chantal.ackermann@biomax.de
In reply to: Neil Conway (#3)

hi,

actually, the major point of my posting was, that the script pg_upgrade
which is part of contrib in 7.3.1 and 7.3.2 is calling pg_dumpall with
an option (-s) that does not exist.

- is this a bug?

regards,
Chantal

#5Lamar Owen
lamar.owen@wgcr.org
In reply to: Chantal Ackermann (#4)

On Monday 10 February 2003 12:52, Chantal Ackermann wrote:

actually, the major point of my posting was, that the script pg_upgrade
which is part of contrib in 7.3.1 and 7.3.2 is calling pg_dumpall with
an option (-s) that does not exist.

You do not need to do a pg_upgrade to go from 7.3.1 to 7.3.2. Your 7.3.1 data
will work fine with 7.3.2. You won't have to pg_upgrade or pg_dumpall until
you move to 7.4 or greater.

- is this a bug?

Possibly.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

#6Tom Lane
tgl@sss.pgh.pa.us
In reply to: Chantal Ackermann (#4)

Chantal Ackermann <chantal.ackermann@biomax.de> writes:

actually, the major point of my posting was, that the script pg_upgrade
which is part of contrib in 7.3.1 and 7.3.2 is calling pg_dumpall with
an option (-s) that does not exist.

Hm. Evidently when Peter rewrote pg_dumpall in C, he was a little too
narrow-minded about which pg_dump options should be accepted by
pg_dumpall. (The old script version would pass through almost anything.)
I wonder if anything else besides -s ought to be added back.

But as to the matter at hand: the fact that no one has tested pg_upgrade
since then should give you a good clue as to (a) its usefulness and (b)
how much you should trust it. The reason it's in contrib and not in the
main distro is that it's unreliable.

regards, tom lane