Downgrading from Postgresql 7.4 to 7.1

[Matt Adams]

Hello:

I have an awkward situation where I must downgrade from 7.4 to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?
Thanks

Matt
--
Matt Adams <ma********@meryships.org> voice [phone]
Systems Engineer, Mercy Ships IOC <http://www.mercyships.org/>

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

[Bruno Wolff III]

On Mon, Apr 19, 2004 at 16:25:21 -0500,
Matt Adams <ma********@mercyships.org> wrote:

Hello:

I have an awkward situation where I must downgrade from 7.4 to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?

You are probably going to have to process the 7.4 dump file before
it can be used to reload the 7.1 database. This shoudln't be too
bad. You might have some performance problems with queries that work
well in 7.4 and not in 7.1. 7.1 doesn't have schemas, so if you were
making use of those you might have to figure out how to get by without
them. You should probably review the release notes for other added
features since 7.1 that you might be using.

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Bruno Wolff III]

On Mon, Apr 19, 2004 at 16:25:21 -0500,
Matt Adams <ma********@mercyships.org> wrote:

Hello:

I have an awkward situation where I must downgrade from 7.4 to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?

You are probably going to have to process the 7.4 dump file before
it can be used to reload the 7.1 database. This shoudln't be too
bad. You might have some performance problems with queries that work
well in 7.4 and not in 7.1. 7.1 doesn't have schemas, so if you were
making use of those you might have to figure out how to get by without
them. You should probably review the release notes for other added
features since 7.1 that you might be using.

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Joe Stump]

I would think if you simply did a pg_dump and then re-imported it you
shouldn't see any problems.

--Joe

-----Original Message-----
From: Matt Adams [mailto:ma********@mercyships.org]
Sent: Monday, April 19, 2004 5:25 PM
To: pg***********@postgresql.org
Subject: [GENERAL] Downgrading from Postgresql 7.4 to 7.1
Hello:

I have an awkward situation where I must downgrade from 7.4
to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?
Thanks

Matt
--
Matt Adams <ma********@meryships.org> voice [phone]
Systems Engineer, Mercy Ships IOC

<http://www.mercyships.org/>

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Joe Stump]

I would think if you simply did a pg_dump and then re-imported it you
shouldn't see any problems.

--Joe

-----Original Message-----
From: Matt Adams [mailto:ma********@mercyships.org]
Sent: Monday, April 19, 2004 5:25 PM
To: pg***********@postgresql.org
Subject: [GENERAL] Downgrading from Postgresql 7.4 to 7.1
Hello:

I have an awkward situation where I must downgrade from 7.4
to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?
Thanks

Matt
--
Matt Adams <ma********@meryships.org> voice [phone]
Systems Engineer, Mercy Ships IOC

<http://www.mercyships.org/>

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Andrew Sullivan]

On Mon, Apr 19, 2004 at 04:25:21PM -0500, Matt Adams wrote:

Hello:

I have an awkward situation where I must downgrade from 7.4 to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?

Almost certainly you'll need to do some fiddling to make the dump
output from 7.4 acceptable to 7.1. My guess is that you'll need to
write some sed or perl do do it adequately for you. You may be in
better shape if you ask pg_dump to use INSERT statements instead, but
be aware that this will at least triple your restore time.

But I also wonder why you want to downgrade that far. 7.1 has
several _really big_ disadvantages. There are plenty of bugs in
there fixed in later versions. Also, 7.1 has the limitation that
VACUUM always blocks, so maintenance of the database will get a whole
lot more expensive (7.1's VACUUM is equivalent to later VACUUM
FULL). Why do you have to do this?

A

--
Andrew Sullivan | aj*@crankycanuck.ca
In the future this spectacle of the middle classes shocking the avant-
garde will probably become the textbook definition of Postmodernism.
--Brad Holland

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

[Andrew Sullivan]

On Mon, Apr 19, 2004 at 04:25:21PM -0500, Matt Adams wrote:

Hello:

I have an awkward situation where I must downgrade from 7.4 to 7.1. I
have two databases already in 7.4. I'm largely ignorant concerning
postgresql: am I going to have any severe problems downgrading?

Almost certainly you'll need to do some fiddling to make the dump
output from 7.4 acceptable to 7.1. My guess is that you'll need to
write some sed or perl do do it adequately for you. You may be in
better shape if you ask pg_dump to use INSERT statements instead, but
be aware that this will at least triple your restore time.

But I also wonder why you want to downgrade that far. 7.1 has
several _really big_ disadvantages. There are plenty of bugs in
there fixed in later versions. Also, 7.1 has the limitation that
VACUUM always blocks, so maintenance of the database will get a whole
lot more expensive (7.1's VACUUM is equivalent to later VACUUM
FULL). Why do you have to do this?

A

--
Andrew Sullivan | aj*@crankycanuck.ca
In the future this spectacle of the middle classes shocking the avant-
garde will probably become the textbook definition of Postmodernism.
--Brad Holland

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org