| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Asychronous database replication |
| Date: | 2005-09-16 11:28:22 |
| Message-ID: | 5745DFDD-632E-43AD-9164-D90C7BBD2028@pgedit.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sep 15, 2005, at 9:54 PM, Greg Stark wrote:
> If you need data to propagate from the clients back to the server
> then things
> get more complicated. Even then you could side step a lot of
> headaches if you
> can structure the application in specific ways, such as
> guaranteeing that the
> clients can only insert, never update records.
And even updates could be OK if the application can support the right
partitioning of the data and only do it one place at a time. With
some kinds of field based work it might be suitable to have global
(read only) data along with data created in the field that is site/
client specific. As long as the data collected in the field is not
being updated on the master, it could continue to be updated in the
field and synced back to the master database.
John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Manes | 2005-09-16 12:34:13 | Re: Asychronous database replication |
| Previous Message | Scott Marlowe | 2005-09-16 04:02:34 | Re: BIG installations of PostgresQL? |