Re: sslcompression / PGSSLCOMPRESSION not behaving as documented? - Mailing list pgsql-general

From Maciek Sakrejda
Subject Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?
Date
Msg-id CAKwe89DhRkHPyMDG35hkAcmKbPokNhQP7zko4bUTg4Eu4Ohnww@mail.gmail.com
Whole thread Raw
In response to Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
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.

On Fri, Jan 16, 2015 at 9:22 AM, Magnus Hagander <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?

pgsql-general by date:

Previous
From: Daniel Begin
Date:
Subject: Re: Indexing large table of coordinates with GiST
Next
From: Adrian Klaver
Date:
Subject: Re: sslcompression / PGSSLCOMPRESSION not behaving as documented?