Re: Unexpected EOF on client connection

From: Howard Cole <howardnews(at)selestial(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: David Boreham <david_list(at)boreham(dot)org>, francisco(at)npgsql(dot)org
Subject: Re: Unexpected EOF on client connection
Date: 2009-12-04 14:07:26
Message-ID: 4B19179E.4030802@selestial.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kern Sibbald 2009-12-04 14:26:08 Re: Catastrophic changes to PostgreSQL 8.4
Previous Message Alvaro Herrera 2009-12-04 13:15:02 Re: Installing PL/pgSQL by default