Re: Win32 max connections bug (causing crashes)

Joshua D. Drake wrote:
> Hello,
> 
> I had a customer call in today they are running Win2003 with 22 gig of 
> ram (that may be a mistype on their end, it may be 32gigs of ram).
> 
> They cranked up their postgresql max_connections to 500.
> 
> When PostgreSQL hits above 400, it dies and I don't mean a slow crawl 
> type death. A death where all connections close and the database does a 
> rollback and restart.
> 
> I was able to reproduce with a simple pgbench on my own win32 environment.
> 
> I wasn't able to go above 300 with mine.

Further on this with Debug 5:

Client:


DEBUG:  name: unnamed; blockState:       DEFAULT; state: INPROGR, 
xid/subid/cid: 19299/1/0, nestlvl: 1, children: <>
DEBUG:  CommitTransaction
DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR, 
xid/subid/cid: 19299/1/0, nestlvl: 1, children: <>
DEBUG:  StartTransactionCommand
DEBUG:  StartTransaction
DEBUG:  name: unnamed; blockState:       DEFAULT; state: INPROGR, 
xid/subid/cid: 19300/1/0, nestlvl: 1, children: <>
DEBUG:  ProcessUtility
DEBUG:  CommitTransactionCommand
DEBUG:  CommitTransaction
DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR, 
xid/subid/cid: 19300/1/0, nestlvl: 1, children: <>
Connection to database 'bench' failed.
server closed the connection unexpectedly        This probably means the server terminated abnormally        before or
whileprocessing the request.
 
jd@scratch:/usr/local/pgsql/bin$


Server to follow in next message.

Joshua D. Drake








> 
> Any thoughts?
> 
> Joshua D. Drake
> 


-- 
   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240   Providing the most comprehensive  PostgreSQL
solutionssince 1997             http://www.commandprompt.com/