pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Florian Pflug <fgp@phlo.org>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Euler Taveira <euler@timbira.com>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq compression
Date: Fri, 15 Jun 2012 19:03:08 +0300
Message-ID: <4FDB5CBC.1030701@enterprisedb.com> (raw)
In-Reply-To: <CABUevEwQeYE1MJGxV-kw5K0iTfaUtSE2r_6C0vZs5a_4CRHpww@mail.gmail.com>
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>
	<CABUevEyv4T+1gR6_Uqm_1qUD9PNDg6UdXbJhwHZgFi9hpQQ6NQ@mail.gmail.com>
	<F3B8BAA6-23E9-423A-A7D1-D2E14769F326@phlo.org>
	<CABUevExi-cJ6AvF2kDOy+qQsB+0JHofrcvVmNVoJ2HziZMMaAg@mail.gmail.com>
	<22690C61-E960-4A2A-BFD5-DAD3D3B5C474@phlo.org>
	<CABUevEzVpqS5RCLz2fFREdPFkuYkEKsrMpnfPixYWPki2=iJOA@mail.gmail.com>
	<4FDB4D0F.6090206@enterprisedb.com>
	<CABUevEyYgnO_zvQT2f8N2ZRZeZ-ZNeW4HxF9AAC3LJqRQrbWUg@mail.gmail.com>
	<4FDB5396.4050402@enterprisedb.com>
	<CABUevEwQeYE1MJGxV-kw5K0iTfaUtSE2r_6C0vZs5a_4CRHpww@mail.gmail.com>

On 15.06.2012 18:28, Magnus Hagander wrote:
> On Fri, Jun 15, 2012 at 11:24 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com>  wrote:
>> On 15.06.2012 17:58, Magnus Hagander wrote:
>>>
>>> On Fri, Jun 15, 2012 at 10:56 PM, Heikki Linnakangas
>>> <heikki.linnakangas@enterprisedb.com>    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



view thread (289+ messages)  latest in thread

Message-ID: <4FDB5CBC.1030701@enterprisedb.com>
Permalink:  ../4FDB5CBC.1030701@enterprisedb.com/
Also on:    postgresql.org/message-id/4FDB5CBC.1030701@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: heikki.linnakangas@enterprisedb.com, magnus@hagander.net, fgp@phlo.org, bruce@momjian.us, tgl@sss.pgh.pa.us, euler@timbira.com
  Subject: Re: libpq compression
  In-Reply-To: <4FDB5CBC.1030701@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox