|
Home > Archive > PostgreSQL Discussion > February 2006 > upgrade PostgreSQL 8.x on production FreeBSD
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
upgrade PostgreSQL 8.x on production FreeBSD
|
|
| pobox@verysmall.org 2006-02-25, 9:44 am |
| Could anybody point to an on-line resource about the steps involved with
upgrading of PostgreSQL 8.x on a production FreeBSD 5.4 with minimum
downtime (i.e. 1 - stop db so that no changes happen 2 - dump 3 -
upgrade (ports) 4 - import 5- start db).
Thanks,
Iv Ray
---------------------------(end of broadcast)---------------------------
TIP 1: 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
| |
| Vivek Khera 2006-02-25, 9:44 am |
|
On Feb 23, 2006, at 9:21 AM, pobox@verysmall.org wrote:
> Could anybody point to an on-line resource about the steps involved
> with upgrading of PostgreSQL 8.x on a production FreeBSD 5.4 with
> minimum downtime (i.e. 1 - stop db so that no changes happen 2 -
> dump 3 - upgrade (ports) 4 - import 5- start db).
Upgrade from what to what?
If you're upgrading from 8.0.x to 8.0.y then there is no dump/reload.
If youre going from < 8.1 to 8.1 then there is dump/reload OR you can
use some sort of replication such as slony to copy the data, then
have a few seconds of downtime while you turn off the older DB and
put the 8.1 in its place.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Alban Hertroys 2006-02-25, 9:44 am |
| pobox@verysmall.org wrote:
> Could anybody point to an on-line resource about the steps involved with
> upgrading of PostgreSQL 8.x on a production FreeBSD 5.4 with minimum
> downtime (i.e. 1 - stop db so that no changes happen 2 - dump 3 -
> upgrade (ports) 4 - import 5- start db).
You want to make your dump with the pg_dump of the new version. I'm not
sure you can build the tools seperately (that'd be excellent, but my
FreeBSD boxes are at home)...
I think it should be:
1 - make postgresql,
2 - make install postgresql-tools
3 - dump
4 - stop db
5 - make install postgresql
6 - restore
7 - start db
--
Alban Hertroys
alban@magproductions
.nl
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
| |
| Philippe Ferreira 2006-02-25, 9:44 am |
| Hi,
If the downtime is a concern, you could use Slony-1 for the migration.
Philippe Ferreira.
>pobox@verysmall.org napisał(a):
>
>
>
>here you are:
>http://www.postgresql.org/docs/8.1/.../migration.html
>
>If both PostgreSQL versions can't coexist on one host, you can use
>another one, with possibly identical setup (HW/OS/etc) for the
>migration, and transfer (use tar + netcat for minimal downtime) the
>cluster afterwards.
>
>
>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Filip Rembiałkowski 2006-02-25, 9:44 am |
| pobox@verysmall.org napisał(a):
> Could anybody point to an on-line resource about the steps involved with
> upgrading of PostgreSQL 8.x on a production FreeBSD 5.4 with minimum
> downtime (i.e. 1 - stop db so that no changes happen 2 - dump 3 -
> upgrade (ports) 4 - import 5- start db).
>
here you are:
http://www.postgresql.org/docs/8.1/.../migration.html
If both PostgreSQL versions can't coexist on one host, you can use
another one, with possibly identical setup (HW/OS/etc) for the
migration, and transfer (use tar + netcat for minimal downtime) the
cluster afterwards.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| pobox@verysmall.org 2006-02-28, 8:28 pm |
| Thank you all for the valuable advices.
I'll try them on a test server and will come back.
Thanks again!
Iv
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
|
|
|
|
|