Re: Using compression on TCP transfer

From: Olivier Gautherot <ogautherot(at)gautherot(dot)net>
To: Andrus <kobruleht2(at)hot(dot)ee>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Using compression on TCP transfer
Date: 2020-03-31 10:28:45
Message-ID: CAJ7S9TWXZZS9LUgcoDVE07v3-AhmuRVz-d-ihCMzkzX1Ja+xQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sorry, forgot the reply all :-)

On Tue, Mar 31, 2020 at 11:39 AM Andrus <kobruleht2(at)hot(dot)ee> wrote:

> Hi,
>
> >See the section about sslcompression in
> https://www.postgresql.org/docs/9.2/libpq-connect.html. It should be your
> answer.
>
> I added
>
> sslcompression=1
>
> to psqlodbc connection string but log file shows that connection is still
> uncompressed:
>
> LOG: connection authorized: user=me database=mydb SSL enabled
> (protocol=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384, bits=256, compression=off)
>
> Maybe because according to TLSv1.3 standard, compression is no more
> allowed or psqlodbc does not pass it to pglib.
>
> How to compress ?
>
> Andrus.
>

Updated doc reference:
https://www.postgresql.org/docs/12/libpq-connect.html

They mention that compression is insecure and disabled by default. Taking
this into account, compression will require that both ODBC and PostgreSQL
are set up with compression enabled. I could not figure out quickly whether
this requires also recompiling the code...

--
Olivier Gautherot
Tel: +33 6 02 71 92 23
https://www.linkedin.com/in/ogautherot/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2020-03-31 11:35:02 Re: Using compression on TCP transfer
Previous Message Andrus 2020-03-31 09:38:54 Re: Using compression on TCP transfer