| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | Mike Christensen <mike(at)kitchenpc(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: peer-to-peer replication with Postgres |
| Date: | 2010-05-11 03:07:38 |
| Message-ID: | AANLkTimlOi-5nnNwmDVKHnbrDgrFURMZlUOc0TAJIFrr@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 10, 2010 at 8:59 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> Scott Marlowe wrote:
>>>
>>> Is there any sort of abstraction layer (like in the driver level) that
>>> can abstract that and just make updates go to one DB and reads
>>> round-robin to other DBs? Hopefully there's a way to make this design
>>> simple to implement.
>>>
>>
>> Pretty sure pgpool can do the "read from these dbs, write to this one".
>>
>
>
> how would it know if you're going to do updates later on in a transaction?
Go here:
http://pgpool.projects.postgresql.org/pgpool-II/doc/pgpool-en.html
look for replicate_select
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-05-11 04:21:16 | Re: Archiver not picking up changes to archive_command |
| Previous Message | John R Pierce | 2010-05-11 02:59:09 | Re: peer-to-peer replication with Postgres |