On Tue, Nov 23, 2010 at 4:42 AM, Mark Gabriel Paylaga
wrote:
> 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 while transaction still
> active
>
>
You have multiple threads sharing the same conn
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 conne
On 11/02/2010 01:42 AM, Jonathan Tripathy wrote:
I would like my application to try and get a connection from the pool,
and if there are none free, wait until either one is free or time is up.
Rather than rolling your own connection pool, consider using one of the
well-established existing on
Thanks! I'll look into it.
On Mon, Sep 6, 2010 at 2:54 PM, Sergey Konoplev wrote:
> Hi,
>
> On 6 September 2010 10:34, Mark Paylaga wrote:
>> Hi sorry if this has been asked already.
>> Is there any mechanism to do connection pooling for libpqxx already?
>> Or any new developments for this?
>>
>
Hi,
On 6 September 2010 10:34, Mark Paylaga wrote:
> Hi sorry if this has been asked already.
> Is there any mechanism to do connection pooling for libpqxx already?
> Or any new developments for this?
>
> Our one dbwriter service instance recieves requests simultaneously to write
> to the databa
