| From: | Cliff Wells <LogiplexSoftware(at)earthlink(dot)net> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Home-brewed table syncronization |
| Date: | 2003-07-09 21:28:57 |
| Message-ID: | 1057786137.15508.29.camel@software1.logiplex.internal |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Wed, 2003-07-09 at 14:14, Michael A Nachbaur wrote:
> So, I'm looking at syncronizing 4 tables from one master database to several
> child databases. I'm thinking of doing the following with DBD::Multiplex:
>
> DELETE FROM TableA;
> INSERT INTO TableA (..) VALUES (...);
> ....
>
> on all the child databases, but I'm not sure what kind of impact this would
> have on my servers. My impression is that this would hammer the indexes, and
> might blow any memory optimization out the window. Only a few records in my
> dataset will change from time-to-time, but just the process of determining
> what is different may take more effort than simply rebuilding.
Keep a timestamp associated with each record. Only update the records
with timestamps later than your last sync.
--
Cliff Wells, Software Engineer
Logiplex Corporation (www.logiplex.net)
(503) 978-6726 (800) 735-0555
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael A Nachbaur | 2003-07-09 21:50:32 | Re: Home-brewed table syncronization |
| Previous Message | Michael A Nachbaur | 2003-07-09 21:14:19 | Home-brewed table syncronization |