Date: Wed, 8 Sep 2010 12:58:17 -0700
From: David Kerr <dmk@mr-paradox.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Smith <greg@2ndquadrant.com>, pgsql-performance@postgresql.org
Subject: Re: pgbench could not send data to client: Broken pipe
Message-ID: <20100908195817.GC49941@mr-paradox.net>
References: <20100908174629.GD40339@mr-paradox.net>
	<8037.1283973026@sss.pgh.pa.us> <4C87E3A6.8060800@2ndquadrant.com>
	<8754.1283975076@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8754.1283975076@sss.pgh.pa.us>
User-Agent: Mutt/1.4.2.3i

On Wed, Sep 08, 2010 at 03:44:36PM -0400, Tom Lane wrote:
- Greg Smith <greg@2ndquadrant.com> writes:
- > Tom Lane wrote:
- >> So I think you could get above the FD_SETSIZE limit with a bit of
- >> hacking if you were using 9.0's pgbench.  No chance with 8.3 though.
- 
- > I believe David can do this easily enough by compiling a 9.0 source code 
- > tree with the "--disable-thread-safety" option.
- 
- It would take a bit more work than that, because the code still tries to
- limit the client count based on FD_SETSIZE.  He'd need to hack it so
- that in non-thread mode, the limit is FD_SETSIZE per subprocess.  I was
- suggesting that an official patch to that effect would be a good thing.

Yeah, that might be beyond me =)

Dave