Hi,
Regarding connection pooling...
I may actually not need connection pooling...
I have one service to write to db. The service receives one or more requests at the same time from different modules.
When two requests are received at the same time, both of the requests will use the same db connection resulting in an error:
Started transaction<READ COMMITTED> while transaction<READ COMMITTED> still active
So what I did was to have dedicated db connections for each type of request. All of these requests are also put in a queue for their respective types so that they will wait for the previous request to finish.
Is this an acceptable solution? Because I tried pgbouncer and it actually does not solve the scenario above....
On Mon, Sep 6, 2010 at 10:12 PM, Mark Gabriel Paylaga
<mpaylaga@gmail.com> wrote:
Thanks! I'll look into it.
On Mon, Sep 6, 2010 at 2:54 PM, Sergey Konoplev <
gray.ru@
gmail.com> wrote: