| From: | Jeff - <threshar(at)torgo(dot)978(dot)org> |
|---|---|
| To: | Grant McLean <grant(at)catalyst(dot)net(dot)nz> |
| Cc: | Peter Wilson <petew(at)yellowhawk(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Slony v. DBMirror |
| Date: | 2005-05-06 13:01:58 |
| Message-ID: | BBB853EE-C3BA-49DD-8DB8-BA3AD69C2768@torgo.978.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On May 5, 2005, at 5:03 PM, Grant McLean wrote:
>
> 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?
>
You'd need to stop client access to PG to prevent changes from
occuring between when you take the dump & when you restore on the
slave and hten fire up dbmirror. Although it might work if you
install the dbmirror triggers, then dump & restore.
Slony uses the COPY interface to read/load data. This is the same
method used by pg_dump so the only throttle will be the network.
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-05-06 13:31:24 | Re: Cursor problem |
| Previous Message | Vidya | 2005-05-06 12:58:11 | Cursor problem |