Tue Jan 25 13:21:20 PST 2005
- Previous message: [Slony1-general] Backing up a PostgreSQL database that is being replicated using Slony
- Next message: [Slony1-general] Backing up a PostgreSQL database that is being replicated using Slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/24/2005 5:14 PM, Fiel Cabral wrote: > On Mon, 24 Jan 2005 15:57:25 -0500, Christopher Browne >> In fact, it seems curious that you would need to do so; are you >> running into such severe failures in your environment that it makes >> sense to routinely recover nodes in this manner? >> > > No. My server application used to not have replication and it was able > to use pg_dump to make backups and restore from those backups using > pg_restore. I was trying to see if I can still get this to work even > if replication is in play. Restoring the origin to an older backup means that your replica is inconsistent anyway and needs to be rebuilt from scratch. How do you envision that the "changes" made by the restore magically turn into replication log information? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] Backing up a PostgreSQL database that is being replicated using Slony
- Next message: [Slony1-general] Backing up a PostgreSQL database that is being replicated using Slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list