From: | Martin Spinassi <martins(dot)listz(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Proxy for postgres |
Date: | 2009-08-14 18:24:13 |
Message-ID: | 1250274253.15094.163.camel@kr0sty.livra.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2009-08-14 at 11:04 -0700, John R Pierce wrote:
> Martin Spinassi wrote:
> > I've been playing around with slony, and as far it didn't make me jump
> > of happiness, I think is my better option to use slony for that,
> > updating just the master, let slony do his job, but allowing the proxy
> > to read from all. Anyway, I'm open to suggestions.
> >
>
> them, yeah, something like pg_pool2 to handle the reads.
So, what you suggest is:
|---------> Master <---|
pg_pool2 ---| |----- Slony
|---------> Slave <---|
Can't figure out if this is gonna work, configuring pg_pool2 to read
both, making slony replicate, and app directly to Master (or pg_pool2
can be configured to write just in one of both?).
Cheers
Martin
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Best | 2009-08-14 18:31:44 | Re: [HACKERS] \copy: unexpected response (4) |
Previous Message | Tom Lane | 2009-08-14 18:04:07 | Re: [HACKERS] \copy: unexpected response (4) |