| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
| Cc: | Robbie Harwood <rharwood(at)redhat(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: libpq compression |
| Date: | 2018-06-22 16:05:43 |
| Message-ID: | 20180622160543.GM4200@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 22, 2018 at 10:18:12AM +0300, Konstantin Knizhnik wrote:
> On 22.06.2018 00:34, Nico Williams wrote:
> >So I think you just have to have lengths.
> >
> >Now, this being about compression, I understand that you might now want
> >to have 4-byte lengths, especially given that most messages will be
> >under 8KB. So use a varint encoding for the lengths.
>
> No explicit framing and lengths are needed in case of using streaming
> compression.
> There can be certainly some kind of frames inside compression protocol
> itself, but it is intrinsic of compression algorithm.
I don't think that's generally true. It may be true of the compression
algorithm you're working with. This is fine, of course, but plugging in
other compression algorithms will require the authors to add framing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-06-22 16:16:18 | Re: [PATCH] Include application_name in "connection authorized" log message |
| Previous Message | Robbie Harwood | 2018-06-22 15:59:17 | Re: libpq compression |