| From: | Uwe Schroeder <uwe(at)bunspace(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org, gnanam(at)zoniac(dot)com |
| Cc: | "'Devrim =?iso-8859-1?q?G=DCND=DCZ=27?=" <devrim(at)gunduz(dot)org> |
| Subject: | Re: How to upgrade PostgreSQL minor releases without a dump/restore? |
| Date: | 2011-03-04 03:43:46 |
| Message-ID: | 201103031943.46705.uwe@bunspace.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> > ? Did you read the paragraph above?
> >
> > Install latest version, and restart postmaster.
>
> Installing of latest version as-is will keep overwriting the existing
> installed directories/files/binaries but not the "/usr/local/pgsql/data/"
> directory right? Since this is our production server database, am just
> clarifying this question that came to my mind, before upgrading.
For sake of safety, I'd always make a backup of the data directory. You don't
need to dump/restore. Just copy the files someplace else and then do the
update. In case something goes wrong you can always go back to your old
version and just copy the backup to the data directory.
That's how I do upgrades. Never needed the backup, but better to have one.
Uwe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukasz Brodziak | 2011-03-04 06:53:43 | Server doesn't listen error |
| Previous Message | Jason Clark | 2011-03-03 16:54:02 | Re: HA warm standby issue with trigger file. |