Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 2751CCE6EC for ; Fri, 15 Jun 2012 13:03:36 -0300 (ADT) Received: from exprod7og114.obsmtp.com ([64.18.2.215]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SfYzh-0007ae-F4 for pgsql-hackers@postgresql.org; Fri, 15 Jun 2012 16:03:35 +0000 Received: from mail-lb0-f177.google.com ([209.85.217.177]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT9tcw0WwORTOOZqT1clxNTIyEJHWf/I1@postini.com; Fri, 15 Jun 2012 09:03:29 PDT Received: by lbbgg6 with SMTP id gg6so3429465lbb.8 for ; Fri, 15 Jun 2012 09:03:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=5f5zU73Wl3nEZbczUZcn6H9tDij5t92A4XO34NKhdpQ=; b=XcpH4v86fkHQ5Ixp8rPyBsGvSDJPADCgJ4zzAJEqNg2B2T09POwa6PehQ1WdWsG5Wu cgomn+NRcOt+kw8QAqW4T9Wcsx2tQE2W8sdqezNH1mODWJ+mDYqPX062+IFBgAh+Ub65 NFnOxpsCi8gW/oPg/jKuFf/tbN7hErk2aJd5HnP1PQscyck6+YtWalqgP+DjST3soWGp uVg+Dtht6MNuTXM46aEdjF/JBqcVUhwSXArqBoXikhHTGxBoF6d2BDuoW6WXzaun0oP8 qmYSnAumWtQLmfpNLlI6mPtr0aGsUu4M/AkHdIrtc5B6fR51Ym/yTLtH/ATDp3TV9f9z 9C9Q== Received: by 10.152.144.138 with SMTP id sm10mr6035174lab.22.1339776193483; Fri, 15 Jun 2012 09:03:13 -0700 (PDT) Received: from [192.168.1.100] (dsl-hkibrasgw2-ff6cc300-200.dhcp.inet.fi. [88.195.108.200]) by mx.google.com with ESMTPS id er3sm6428658lbb.16.2012.06.15.09.03.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Jun 2012 09:03:12 -0700 (PDT) Message-ID: <4FDB5CBC.1030701@enterprisedb.com> Date: Fri, 15 Jun 2012 19:03:08 +0300 From: Heikki Linnakangas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4 MIME-Version: 1.0 To: Magnus Hagander CC: Florian Pflug , Bruce Momjian , Tom Lane , Euler Taveira , Pgsql Hackers Subject: Re: libpq compression References: <4FD9698F.2090407@timbira.com> <29853.1339651170@sss.pgh.pa.us> <4FD9E70B.9040607@timbira.com> <11502.1339699384@sss.pgh.pa.us> <20120615021938.GA21704@momjian.us> <22690C61-E960-4A2A-BFD5-DAD3D3B5C474@phlo.org> <4FDB4D0F.6090206@enterprisedb.com> <4FDB5396.4050402@enterprisedb.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQknMwepTp5vqFtY1Bxrp3SAGUOVyJM+y1eBj0U54Bi9WBcdvYh6F05I+SXkRCN8NkE8HO+m X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201206/729 X-Sequence-Number: 209569 On 15.06.2012 18:28, Magnus Hagander wrote: > On Fri, Jun 15, 2012 at 11:24 PM, Heikki Linnakangas > wrote: >> On 15.06.2012 17:58, Magnus Hagander wrote: >>> >>> On Fri, Jun 15, 2012 at 10:56 PM, Heikki Linnakangas >>> wrote: >>>> >>>> You could write a dummy SSL implementation that only does compression, >>>> not >>>> encryption. Ie. only support the 'null' encryption method. That should be >>>> about the same amount of work as writing an implementation of compression >>>> using whatever protocol we would decide to use for negotiating the >>>> compression. >>> >>> Sure, but then what do you do if you actually want both? >> >> Umm, then you use a real SSL libray, not the dummy one? > > But (in this scenario, and so far nobody has proven it to be wrong) > there exists no real SSL library that does support compression. Oh, I see. Then you're screwed. But I think the right solution to that is to write/extend a Java SSL implementation to support compression, not to invent our own in PostgreSQL. The JDK is open source nowadays. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com