Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?
Adrian Klaver <adrian.klaver@aklaver.com>
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Maciek Sakrejda <maciek@heroku.com>, Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Date: 2015-01-16T18:52:20Z
Lists: pgsql-general
On 01/16/2015 10:34 AM, Maciek Sakrejda wrote: > Thanks, everyone. That seems to be it. I still haven't gotten it to work > (I tried setting OPENSSL_DEFAULT_ZLIB=true in > /etc/postgresql/9.2/main/environment and restarting the server, then > adding the same env var when connecting with the client), but now that I > know where the problem is, I think I can work through it. I think environment is for the PG specific env variables that postmaster/postgres understands: http://www.postgresql.org/docs/9.2/interactive/app-postgres.html OPENSSL_DEFAULT_ZLIB is a system env variable, you will need to set in the shell. > > On Fri, Jan 16, 2015 at 9:22 AM, Magnus Hagander <magnus@hagander.net > <mailto:magnus@hagander.net>> wrote: > > There's been a few reports on this now. Perhaps we should add a note > to the docs (not necessarily saying how to fix it, as it may differ, > but a note saying that many distributions changed the way this is > handled and that you might need to set an external override)? > > > That would definitely have helped me, yes. I'd submit a doc patch, but > I'm not sure what the right language would be here. Are there other > similar caveats documented elsewhere I could crib from? -- Adrian Klaver adrian.klaver@aklaver.com