X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 19606D8D46 for ; Tue, 13 Sep 2005 16:21:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48916-07 for ; Tue, 13 Sep 2005 19:21:29 +0000 (GMT) Received: from www.epot.cz (sramek.casablanca.cz [81.0.254.161]) by svr1.postgresql.org (Postfix) with ESMTP id 520D0D86F2 for ; Tue, 13 Sep 2005 16:21:28 -0300 (ADT) Received: from www.epot.cz (localhost [127.0.0.1]) by www.epot.cz (8.13.3/8.12.10) with ESMTP id j8DJLN0Y005473; Tue, 13 Sep 2005 21:21:23 +0200 (CEST) (envelope-from dali@insula.cz) Received: (from xsramek01@localhost) by www.epot.cz (8.13.3/8.12.10/Submit) id j8DJLKA3005472; Tue, 13 Sep 2005 21:21:20 +0200 (CEST) (envelope-from dali@insula.cz) X-Authentication-Warning: www.epot.cz: xsramek01 set sender to dali@insula.cz using -f Date: Tue, 13 Sep 2005 21:21:20 +0200 From: Dalibor Sramek To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Low performance on Windows problem Message-ID: <20050913192120.GA5370@www.epot.cz> References: <6EE64EF3AB31D5448D0007DD34EEB3417DD312@Herge.rcsinc.local> <20050913134951.GA53837@www.epot.cz> <23481.1126625522@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23481.1126625522@sss.pgh.pa.us> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned-By: Clam AntiVirus - OK X-Scanned-By: MIMEDefang 2.52 on 81.0.254.161 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 required=5 tests=[AWL=-0.000, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200509/172 X-Sequence-Number: 14480 On Tue, Sep 13, 2005 at 11:32:02AM -0400, Tom Lane wrote: > So it's a networking issue. I haven't paid real close attention to > ... > updates. Check through the list archives ... This one http://archives.postgresql.org/pgsql-performance/2005-06/msg00593.php seems to be very similar to my problem. Somebody suggested that setting TCP_NODELAY option to the TCP connection may help. Before I dive into the source: could some win-pg guru tell me if the Windows server tries to set this option? Is it possible to change it via configuration? Is there a way to find out if the TCP_NODELAY option was actually used for a connection? Anyway thank you all. I believe I am getting closer to a solution. Dalibor Sramek -- Dalibor Sramek http://www.insula.cz/dali \ In the eyes of cats / dalibor.sramek@insula.cz \ all things / >H blog http://www.transhumanismus.cz/blog.php \ belong to cats.