Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 56A7A632954
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Sun,  1 Mar 2009 13:43:33 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 03319-10
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Sun,  1 Mar 2009 13:43:30 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 7F0B96325CE
	for <pgsql-performance@postgresql.org>;
	Sun,  1 Mar 2009 13:43:30 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n21HhIpC013122;
	Sun, 1 Mar 2009 12:43:18 -0500 (EST)
To: Linos <info@linos.es>
cc: "Ross J. Reedstrom" <reedstrm@rice.edu>, pgsql-performance@postgresql.org
Subject: Re: TCP network cost 
In-reply-to: <49AAC6AC.60309@linos.es> 
References: <1ca1c1410902171013q478f2620n13fcd68cb8b3d911@mail.gmail.com>
	<20090217070403.GB2486@cooker>
	<3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>
	<alpine.DEB.1.10.0902170032440.25606@asgard.lang.hm>
	<20090217070403.GB2486@cooker>
	<3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>
	<20090217200416.GA23707@cooker> <87hc2r272g.fsf@oxford.xeocode.com>
	<20090223194212.GA14802@cooker> <27042.1235423820@sss.pgh.pa.us>
	<20090224170201.GA25420@cooker> <49AAC6AC.60309@linos.es>
Comments: In-reply-to Linos <info@linos.es>
	message dated "Sun, 01 Mar 2009 18:32:28 +0100"
Date: Sun, 01 Mar 2009 12:43:18 -0500
Message-ID: <13121.1235929398@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200903/3
X-Sequence-Number: 32925

Linos <info@linos.es> writes:
> Hello, i have been having a problem like this in debian machines and i have 
> discovered that (almost in my case), the problem only arises when i am using 
> "ssl = true" in postgresql.conf although i am using clear tcp connections to 
> localhost to perform my query, if i disable ssl in configuration my localhost 
> query times goes from 4200ms to 110ms,

Does that number include connection startup overhead?  (If it doesn't,
it'd be pretty strange.)  Ross's problem is not about startup overhead,
unless I've misread him completely.

			regards, tom lane