| From: | Grant McLean <grant(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Jeff - <threshar(at)torgo(dot)978(dot)org> |
| Cc: | Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Slony v. DBMirror |
| Date: | 2005-05-05 21:03:43 |
| Message-ID: | 1115327023.11257.9.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2005-05-05 at 14:16 -0400, Jeff - wrote:
> One of the biggest things for Slony is that you can install slony,
> set things up and it will bring the slave(s) "up to speed". You
> don't need to do an initial data dump (I think you still need to load
> the schema on the slaves, but not the data). That is a BIG win for
> us folks who can't take a machine down while pg_dump runs (and while
> it is restored on hte slave)
Why would you need to take anything down to run pg_dump? And surely
bringing a slave up to speed using Slony would be much slower than
dump/restore?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | typing80wpm | 2005-05-05 21:17:06 | Adventures in Quest for GUI RAD |
| Previous Message | Ying Lu | 2005-05-05 20:37:58 | "current transaction is aborted, commands ignored until end of transaction block" Error |