From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Compression on SSL links? |
Date: | 2010-08-13 15:38:53 |
Message-ID: | 24975.1281713933@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> Overall: it sounds to me like SSL/TLS level compression would only be
> useful for native libpq-to-postgresql connections, and probably wouldn't
> be usable for non-libpq based database access drivers. It'd only work if
> SSL was configured, which is a limitation it'd be nice to avoid.
I don't really see that. The case where it's sensible to use
compression on the connection is where you're pushing data across
a WAN. That's also pretty much exactly the situation where it's
sensible to use encryption. I guess there'd be a use case for
compression-without-encryption if you had a trustworthy private WAN,
but who's got one of those?
So I'm much more in favor of doing something like this than doing it
directly in our own protocol.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2010-08-13 15:56:15 | Re: Compression on SSL links? |
Previous Message | Peter Hunsberger | 2010-08-13 15:14:19 | Re: ORM integration? |