Fri May 16 07:29:14 PDT 2008
- Previous message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Next message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, May 16, 2008 at 04:16:32PM +0200, Jacques Caron wrote: > representation of data. So you can't use it for transparent upgrade > scenarios. > > Correct me if I'm wrong. No, you're right. The only real way to upgrade Postgres today without a complete dump and restore is some sort of trigger-based replication (like Slony). I don't know whether Bucardo or Londiste can do the same trick, but their design suggests they might be able to. I also used erserver in the past to do this, although that was way harder and much scarier. A
- Previous message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Next message: [Slony1-general] Using Postgres' continuous archiving and point-in-time recovery as a form of replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list