Re: libpq compression (part 2)

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Daniil Zakhlystov <usernamedt(at)yandex-team(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: libpq compression (part 2)
Date: 2022-01-12 09:38:55
Message-ID: EC946E6B-DEC1-4318-8475-E4584E09EE61@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 8 янв. 2022 г., в 01:56, Stephen Frost <sfrost(at)snowman(dot)net> написал(а):
>>
>> It's discussed in last year's thread. The thinking is that there tends to be
>> *fewer* exploitable opportunities between application->DB than between
>> browser->app.
>
> Yes, this was discussed previously and addressed.

What else do we need to decide architecturally to make protocol compression happen in 15? As far as I can see - only HBA\GUC part.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-01-12 09:54:31 Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
Previous Message Amit Kapila 2022-01-12 09:38:22 Re: row filtering for logical replication