| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Jacob Burroughs <jburroughs(at)instructure(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: libpq compression (part 3) |
| Date: | 2024-05-21 12:32:56 |
| Message-ID: | CA+TgmoYjfiUN_uD1NUWqqx=vLUcUXBKC9C85wSqXhwL67=maNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 20, 2024 at 4:12 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> That used to be the case in HTTP/1. But header compression was one of the headline features of HTTP/2, which isn't exactly new anymore. But there's a special algorithm, HPACK, for it. And then http/3 uses QPACK. Cloudflare has a pretty decent blog post explaining why and how: https://blog.cloudflare.com/hpack-the-silent-killer-feature-of-http-2/, or rfc7541 for all the details.
>
> tl;dr; is yes, let's be careful not to expose headers to a CRIME-style attack. And I doubt our connections has as much to gain by compressing "header style" fields as http, so we are probably better off just not compressing > Work: https://www.redpill-linpro.com/
What do you think constitutes a header in the context of the
PostgreSQL wire protocol?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-05-21 12:34:56 | Re: Path to unreverting "Allow planner to use Merge Append to efficiently implement UNION" |
| Previous Message | Ranier Vilela | 2024-05-21 12:32:42 | Re: Convert node test compile-time settings into run-time parameters |