From: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
---|---|
To: | Daniil Zakhlystov <usernamedt(at)yandex-team(dot)ru> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Subject: | Re: libpq compression |
Date: | 2020-11-24 12:32:53 |
Message-ID: | 612f227d-cb27-9238-5922-1500f8b2eb96@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Based on Andres review I have implemented the following changes in
libpq_compression:
1. Make it possible to specify list of compression algorithms in
connection string.
2. Make it possible to specify compression level.
3. Use "_pq_.compression" instead of "compression" in startup package.
4. Use full names instead of one-character encoding for compression
algorithm names.
So now it is possible to open connection in this way:
psql "dbname=postgres compression=zstd:5,zlib"
New version of the patch is attached.
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment | Content-Type | Size |
---|---|---|
libpq-compression-26.patch | text/x-patch | 69.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2020-11-24 13:44:08 | Re: [HACKERS] Custom compression methods |
Previous Message | Magnus Hagander | 2020-11-24 12:32:45 | Re: Prevent printing "next step instructions" in initdb and pg_upgrade |