Re: Some thoughts on replication

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Dirk Heinrichs <heini(at)chaos(dot)tng(dot)oche(dot)de>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Some thoughts on replication
Date: 2001-01-27 18:12:23
Message-ID: 200101271812.NAA11578@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> Am Samstag, 27. Januar 2001 00:20 schrieb Bruce Momjian:
> > > Have you looked at the replication code that is in contrib?
> >
> > Yes, your description sounds just like it.
>
> Hmm, which of the two? The trigger mechanism?

The triggers.

>
> In the meantime, a third solution came to my mind:
>
> In case somebody has to take a database with him on a laptop, it is hard to
> do replication and avoid conflicts. I once saw an insurance application,
> based on FoxPro, where the insurance agents could select the data of the
> customers he wanted to visit and and create a so called child database, which
> had exactly he same tables as the "mother" and exactly those rows with data
> related to the selected customers. Those rows where the marked as readonly in
> the mother database, so that only the data in the child db could be changed.
> Later, the changes in th child db was reintegrated into the mother db and the
> child was deleted.

Yes, that is a data partitioning feature of replication.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Davis 2001-01-27 18:27:58 RE: Admin tutorials?
Previous Message Bruce Momjian 2001-01-27 18:11:02 Re: postgres limitation