On 05/08/2014 09:58 PM, Krystian Bigaj wrote:
I've build OpenSSL with zlib (perl Configure VC-WIN32 no-asm zlib-dynamic --prefix=...) and now compression works correctly.After executing: SELECT lpad('', 1024*1024, 'A') there is only about 13kB of TCP transfer instead of ~1MB. Thanks again! However I'm still curious why windows build doesn't have this enabled by default. Is it a potential compatibility issues, or just an oversight?
This probably a question for EnterpriseDB who builds the Windows binaries. They have a forum for installer issues that might be a good place to start:
http://forums.enterprisedb.com/forums/show/9.page
I would like to see a note in docs about that issue. I've read that docs about sslcompression before, also I knew that PG on Windows is build with zlib support (for pg_dump/pg_restore), and because of this I wrongly assumed that OpenSSL is build with zlib too. Additionally that "Encryption=SSL encrypted" and "SSL Compression=yes" in pgAdmin made me think that it's a bug in PG. Best regards, Krystian Bigaj
-- Adrian Klaver adrian.kla...@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
