| From: | Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com> |
|---|---|
| To: | Geoffrey <lists(at)serioustechnology(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [OT] Slony (initial) Replication - Slow |
| Date: | 2008-01-04 02:44:14 |
| Message-ID: | 1199414654.15270.1.camel@neuromancer.home.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2008-01-03 at 19:17 -0500, Geoffrey wrote:
> Ow Mun Heng wrote:
> > However during the startup of slony, I noticed that it issues a truncate
> > command to the (to be) replicated table. Hence, this means that there's
> > no such need for me to do a dump/restore in the 1st place.
> >
> This is correct. You want an empty replication database. When you
> start replication slony will bring the master and slave into sync.
>
Thanks to you and others who has responded for confirmation.
I would additionally like to know if there was any way for me to use the
dump/restore method and have slony pick up where it was left off?
BTW, it's working right now after some unsuccessful attempts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fernando Hevia | 2008-01-04 03:57:12 | Re: [SQL] Argentinian timezone change at the last moment. How to change pgsql tz db? |
| Previous Message | Tom Lane | 2008-01-04 00:52:17 | Re: SQLSTATE code for duplicate constraint |