Re: Disable OpenSSL compression

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Magnus Hagander <magnus(at)hagander(dot)net>, "Christopher Browne *EXTERN*" <cbbrowne(at)gmail(dot)com>, ktm(at)rice(dot)edu, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Disable OpenSSL compression
Date: 2011-11-10 22:39:18
Message-ID: 201111102239.pAAMdIU09587@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > How is the compression connection parameter set? It seems odd for it to
> > be compiled into the application because the application could be run on
> > different networks. I don't know of any way to inject connection
> > options from outside the application like libpq's PGOPTIONS.
>
> Huh? You put it in the connection string, typically. This is not
> different from how you'd specify sslmode to start with.

Well, you are saying the client is more flexible, but if the client is a
binary, it isn't flexible without an environment variable to control it.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Karlsson 2011-11-10 22:42:18 Re: Parsing output of EXPLAIN command in PostgreSQL
Previous Message Greg Smith 2011-11-10 22:26:11 Re: Parsing output of EXPLAIN command in PostgreSQL