| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pgbouncer |
| Date: | 2010-06-03 20:33:46 |
| Message-ID: | AANLkTim5fsgfNOQ77dZ4r64UCp1JjPpUMVRU0GK223b-@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 3, 2010 at 4:03 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> I'm interested in this too...does anyone else have experience in this matter?
>
I've pondered this many times. My questions are what failure mode are
you looking to avoid, especially if you're using pgbouncer for load
balance in addition to connection pool. I think the best spot in most
cases is the web server itself, but If the web server is dead, then
the pooler goes with it, whereas if the pooler is elsewhere you have
yet another point of failure when load balancing -- that is if db1
goes down and takes pgpool with it, db2 is unused and won't save your
app.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wang, Mary Y | 2010-06-03 23:05:14 | How to remove the current database and populate the database with new data? |
| Previous Message | Alvaro Herrera | 2010-06-03 20:30:53 | Re: Removing CONTEXT from RAISE EXCEPTION messages from triggers |