On Fri, Apr 28, 2023 at 9:03 AM Magnus Hagander wrote:
> On Thu, Apr 27, 2023 at 11:55 AM Laurenz Albe
> wrote:
> >
> > 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 fi
On Thu, Apr 27, 2023 at 11:55 AM Laurenz Albe wrote:
>
> 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 ov
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 reco
On Thu, Apr 27, 2023 at 11:24 AM Laurenz Albe
wrote:
> On Thu, 2023-04-27 at 14:48 +0530, Tushar Takate wrote:
> > Does PostgreSQL support in-transit compression for a client connection?
>
> No, not any more.
>
On a related but different subject, as someone who must store ZLIB (from
ZIP files)
a
On Thu, 2023-04-27 at 14:48 +0530, Tushar Takate wrote:
> Does PostgreSQL support in-transit compression for a client connection?
No, not any more. There used to be compression via SSL, but that was
removed for security reasons, and because most binary distributions of
OpenSSL didn't support it a
> On 27 Apr 2023, at 11:18, Tushar Takate wrote:
> Does PostgreSQL support in-transit compression for a client connection?
No. Earlier versions supported SSL compression for encrypted connections but
that rarely worked as it was disabled in the vast majority of all OpenSSL
installations. There
