From karl@denninger.net Sat Oct 20 01:10:38 2012 Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TPNaI-0002A3-Gc for pgsql-performance@postgresql.org; Sat, 20 Oct 2012 01:10:38 +0000 Received: from wsip-70-169-168-7.pn.at.cox.net ([70.169.168.7] helo=FS.denninger.net) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TPNaC-0007mi-Bt for pgsql-performance@postgresql.org; Sat, 20 Oct 2012 01:10:37 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.4/8.13.1) with ESMTP id q9K1AUY9015596 for ; Fri, 19 Oct 2012 20:10:30 -0500 (CDT) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Fri Oct 19 20:10:30 2012 Message-ID: <5081FA00.2010409@denninger.net> Date: Fri, 19 Oct 2012 20:10:24 -0500 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: Connection Options -- SSL already uses compression? X-Enigmail-Version: 1.4.5 Content-Type: multipart/alternative; boundary="------------020101000900030102030601" X-Antivirus: avast! (VPS 121019-1, 10/19/2012), Outbound message X-Antivirus-Status: Clean X-Pg-Spam-Score: -0.9 (/) X-Archive-Number: 201210/278 X-Sequence-Number: 48237 This is a multi-part message in MIME format. --------------020101000900030102030601 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by FS.denninger.net id q9K1AUY9015596 Am I reading this correctly -- it appears that if SSL negotiation is enabled for a connection (say, when using pg_basebackup over a WAN) that compression /*is automatically used*/ (provided it is supported on both ends)? Is there a way to check and see if it _*is*_ on for a given connection? I was looking to hack in zlib support and saw that appears to be already-present support, provided SSL connection security is enabled. --=20 -- Karl Denninger /The Market Ticker =AE/ Cuda Systems LLC --------------020101000900030102030601 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Am I reading this correctly -- it appears that if SSL negotiation is enabled for a connection (say, when using pg_basebackup over a WAN) that compression is automatically used (provided it is supported on both ends)?

Is there a way to check and see if it is on for a given connection?

I was looking to hack in zlib support and saw that appears to be already-present support, provided SSL connection security is enabled.

--
-- Karl Denninger
The Market Ticker ®
Cuda Systems LLC
--------------020101000900030102030601-- From magnus@hagander.net Sun Oct 21 07:51:10 2012 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TPqJS-0000gu-8q for pgsql-performance@postgresql.org; Sun, 21 Oct 2012 07:51:10 +0000 Received: from mail-la0-f46.google.com ([209.85.215.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TPqJM-0000dn-JG for pgsql-performance@postgresql.org; Sun, 21 Oct 2012 07:51:08 +0000 Received: by mail-la0-f46.google.com with SMTP id h6so1040407lag.19 for ; Sun, 21 Oct 2012 00:51:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8AWkekRmA8QtthQMZLshwWQKRE36pHdoyHsLRlXPbjU=; b=Qw4nj9fztOpkeddK+p/bhxihf8RknW+GjioDo6GhEqUU5QdwOMjobPVQaiUSvSTdxO DpvHN9jRlc4ftV+ZhMA8DvEa4NOtUl43y9xouNQKs0m03Oui+UMH3pmxyrRODxdGFFON phfxJVm2KtDWI/2rBvtur+jjNUWu0jzuWSUDvdBSHdMTsfcXR39Ywh8rr9XWcdPoZU3o XK6ThMBD/YaBsS3scsmgSOoSQKzsTAfwuGLhTT2f84W1RR1hVTd2Uou3qmMI1M5ZljST EFXvw2vdnXa6q+a/00r0ZP3+plxmvAPuiB1mQjZdOfORlYQoMVLWIGixTbddmTa7a9hF s6Gg== MIME-Version: 1.0 Received: by 10.112.38.65 with SMTP id e1mr2440859lbk.15.1350805863786; Sun, 21 Oct 2012 00:51:03 -0700 (PDT) Received: by 10.152.130.169 with HTTP; Sun, 21 Oct 2012 00:51:03 -0700 (PDT) In-Reply-To: <5081FA00.2010409@denninger.net> References: <5081FA00.2010409@denninger.net> Date: Sun, 21 Oct 2012 09:51:03 +0200 Message-ID: Subject: Re: Connection Options -- SSL already uses compression? From: Magnus Hagander To: Karl Denninger Cc: "pgsql-performance@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnj+899GrRzRDfxBua0aUOK4Co+1IkKYpTGa36NWBylPEPht7tBhtbOy0UxCRDe/mZW3sXU X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201210/279 X-Sequence-Number: 48238 On Sat, Oct 20, 2012 at 3:10 AM, Karl Denninger wrote: > Am I reading this correctly -- it appears that if SSL negotiation is enabled > for a connection (say, when using pg_basebackup over a WAN) that compression > is automatically used (provided it is supported on both ends)? That would depend on the OpenSSL defaults, I believe. Pretty sure you can configure that system wide. > Is there a way to check and see if it is on for a given connection? You can use PQgetssl() and then use OpenSSL functions to get the info from there. I'm not sure exactly how, but it would surprise me if it's not possible. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/