From: | Daniel Migowski <dmigowski(at)ikoffice(dot)de> |
---|---|
To: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Configurable Send/Receive Buffer Sizes |
Date: | 2011-04-27 12:02:40 |
Message-ID: | 41ED3F5450C90F4D8381BC4D8DF6BBDC4F099DF1@EXCHANGESERVER.ikoffice.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I fully support this request! I currently have a overridden PGStream in my Classpath to be able to set it manually to 128k. Else our update scripts hang for the same reason. Making this configurable would be of great help.
Regards,
Daniel Migowski
________________________________________
Von: pgsql-jdbc-owner(at)postgresql(dot)org [pgsql-jdbc-owner(at)postgresql(dot)org]" im Auftrag von "Bernd Helmle [mailings(at)oopsware(dot)de]
Gesendet: Donnerstag, 21. April 2011 17:16
An: Kevin Grittner; pgsql-jdbc(at)postgresql(dot)org
Betreff: Re: [JDBC] Configurable Send/Receive Buffer Sizes
--On 21. April 2011 09:49:54 -0500 Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
wrote:
> Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
>
>> An interesting example is the small test program from
>>
>> <http://archives.postgresql.org/pgsql-jdbc/2008-10/msg00045.php>
>>
>> which could be make working with the appropiate buffer settings.
>
>> I didn't invest any time on benchmarks, but maybe there's also
>> some value in it performance-wise.
>
> So the primary point is to avoid deadlocks on full network buffers?
>
Yeah, that was the primary idea...or, well, to workaround them. You could argue
that its still possible to run into those issue, but less likely. With the
proper settings it didn't occur to me again, though.
--
Thanks
Bernd
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
From | Date | Subject | |
---|---|---|---|
Next Message | digifork | 2011-04-27 17:59:48 | PGStream.ReceiveTupleV3 and Out of Memory |
Previous Message | Kevin Grittner | 2011-04-25 21:06:45 | Re: Unnessecary use of new Integer(n) in AbstractJdbc2ResultSet |