Re: PostgreSQL in-transit compression for a client connection - Mailing list pgsql-general

From Laurenz Albe
Subject Re: PostgreSQL in-transit compression for a client connection
Date
Msg-id 5be87a471484600306d4e4922a6587fc9a6bf3b7.camel@cybertec.at
Whole thread Raw
In response to Re: PostgreSQL in-transit compression for a client connection  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: PostgreSQL in-transit compression for a client connection
List pgsql-general
On Thu, 2023-04-27 at 11:44 +0200, Dominique Devienne wrote:
> as someone who must store ZLIB (from ZIP files)
> and sometimes LZ4 compressed `bytea` values, I often find it's a shame that I have
> to decompress them, send them over the wire uncompressed, to have the PostgreSQL
> backend recompress them when TOAST'ed. That's a waste of CPU and IO bandwidth...

That's not what you were looking for, but why not store the compressed data
in the database (after SET STORAGE EXTERNAL on the column) and uncompress
them after you have received them on the client side?

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: PostgreSQL in-transit compression for a client connection
Next
From: gzh
Date:
Subject: Re:Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist