Re: 8.2.3: Server crashes on Windows using Eclipse/Junit

From: Dave Page <dpage(at)postgresql(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Trevor Talbot <quension(at)gmail(dot)com>, Rainer Bauer <usenet(at)munnin(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 8.2.3: Server crashes on Windows using Eclipse/Junit
Date: 2007-10-22 20:19:16
Message-ID: 471D05C4.8010104@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Dave Page wrote:
> So the only other changes I can think of that might affect things are
> the VC++ build or the shared memory changes, though I can't see why they
> would cause problems offhand. I'll go try a mingw build...

mingw build of stock 8.3b1, no configure options specified at all,
consumes 3.2KB of desktop heap per connection.

So, it's either something we're doing different with the VC++
compile/link options, or it's the VC8 runtimes using more resources.

Oh, and I still see the second limitation where it bombs out over about
125 connections, so that isn't build/runtime specific.

Shall we take this over to -hackers btw?

/D

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Trevor Talbot 2007-10-22 20:19:24 Re: 8.2.3: Server crashes on Windows using Eclipse/Junit
Previous Message Magnus Hagander 2007-10-22 20:16:38 Re: 8.2.3: Server crashes on Windows using Eclipse/Junit

Browse pgsql-hackers by date

  From Date Subject
Next Message Trevor Talbot 2007-10-22 20:19:24 Re: 8.2.3: Server crashes on Windows using Eclipse/Junit
Previous Message Magnus Hagander 2007-10-22 20:16:38 Re: 8.2.3: Server crashes on Windows using Eclipse/Junit