Re:Harder, Better, Faster, Stronger: New Features in Postgre...
by chrisbolt on Friday April 24, 2009 @12:42PM
(#577743)
One thing I've never liked about postgres is that for any major version upgrade (8.3 -> 8.4) you need to do a full dump and restore of all your data. How do people handle this?
[ Parent
| on HN ]
Re:Harder, Better, Faster, Stronger: New Features in Postgre...
by nimbix on Friday April 24, 2009 @12:52PM
(#577757)
We do it over the weekend. Or at night. Or both. It's not fun, but we can handle it once every year and a half.
I considered using Slony replication the last time we were upgrading to copy data between the databases, but I figured it doesn't make much difference and did a dump/restore instead.
Re:Harder, Better, Faster, Stronger: New Features in Postgre...
by boundlessdreamz on Saturday April 25, 2009 @01:54AM
(#578671)
oh! So what happens when you run apt-get upgrade or something similar ?
1. Will the upgrade fails because there are running databases?
2. Or can you dump using the new DB version and restore again ?
Upgrading mysql was a breeze.