| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Tushar Takate <tushar11(dot)takate(at)gmail(dot)com>, daniel(at)yesql(dot)se |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL in-transit compression for a client connection |
| Date: | 2023-04-27 09:55:15 |
| Message-ID: | 5be87a471484600306d4e4922a6587fc9a6bf3b7.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gzh | 2023-04-27 11:20:41 | Re:Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist |
| Previous Message | Dominique Devienne | 2023-04-27 09:44:05 | Re: PostgreSQL in-transit compression for a client connection |