| From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
|---|---|
| To: | Kirk Strauser <kirk(at)strauser(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why would I want to use connection pooling middleware? |
| Date: | 2009-01-15 16:20:51 |
| Message-ID: | 20090115112051.6bb2a910.wmoran@potentialtech.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kirk Strauser <kirk(at)strauser(dot)com> wrote:
[snip]
> I understand why pooling within a process itself is a good thing.
> However, say I have two users running the same program on different
> desktop machines. At present, those applications connect with the
> same username/password that's tied to the program and not the actual
> user. It seems like if Abby and Barb end up sharing the same
> connection from the pool, and Abby runs some giant report query, then
> Barb would get held back while she waits for it to finish. Is that
> true?
I don't believe that's true. My understanding of pgpool is that it will
reuse an existing connection if it's free, or open a new one if required.
--
Bill Moran
http://www.potentialtech.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirk Strauser | 2009-01-15 16:26:35 | Re: Why would I want to use connection pooling middleware? |
| Previous Message | Christopher Browne | 2009-01-15 16:17:21 | Re: Why would I want to use connection pooling middleware? |