Re: Unexpected EOF on client connection - Mailing list pgsql-general

From Howard Cole
Subject Re: Unexpected EOF on client connection
Date
Msg-id 4B19179E.4030802@selestial.com
Whole thread Raw
In response to Re: Unexpected EOF on client connection  (David Boreham <david_list@boreham.org>)
List pgsql-general
David Boreham wrote:
>> Sampling the number of connections on my database I decided that the
>> number of connections settled at 6 so I changed my MinPoolSize from 3
>> to 6. I checked the current state of the database and the number of
>> connections is currently 12. Tonight I shall change the MinPoolSize
>> to 8 and I am wondering if the number of connections used is going to
>> appear as 16!
>>
> Pretty soon you'll discover that you have two instances of the pool :)
>
lol.

Changed the MinPoolSize and the number of connections is exactly the
pool size at the moment. So no doubling up this time. The npgsql pooling
appears to be working as expected. The errors are still appearing in the
log.

What happens to new connections that exceed the pool size? Are the
connections added to the pool briefly, or are they created outside the
pool and allowed to timeout on their own? Also are the pooled
connections set to renew if they timeout, or do they never timeout?


pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Installing PL/pgSQL by default
Next
From: Tom Lane
Date:
Subject: Re: Catastrophic changes to PostgreSQL 8.4