From: | David Kerr <dmk(at)mr-paradox(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pgbench could not send data to client: Broken pipe |
Date: | 2010-09-08 19:58:17 |
Message-ID: | 20100908195817.GC49941@mr-paradox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Sep 08, 2010 at 03:44:36PM -0400, Tom Lane wrote:
- Greg Smith <greg(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-08 20:35:28 | Re: pgbench could not send data to client: Broken pipe |
Previous Message | David Kerr | 2010-09-08 19:56:54 | Re: pgbench could not send data to client: Broken pipe |