From: Bruce Momjian <bruce@momjian.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Daniil Zakhlystov <usernamedt@yandex-team.ru>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: libpq compression (part 2)
Date: Fri, 7 Jan 2022 16:09:37 -0500
Message-ID: <YdisEaJaBENLmOti@momjian.us> (raw)
In-Reply-To: <20220107205638.GP15820@tamriel.snowman.net>
References: <ABAA09C6-BB95-47A5-890D-90353533F9AC@yandex-team.ru>
<20220101172504.GW24477@telsasoft.com>
<YdiKaL/AhNV9OtvK@momjian.us>
<20220107192110.GG14051@telsasoft.com>
<20220107205638.GP15820@tamriel.snowman.net>
On Fri, Jan 7, 2022 at 03:56:39PM -0500, Stephen Frost wrote:
> As for the details of how we allow control over it, I suppose there's a
> number of options. Having it in the HBA doesn't seem terrible, though I
> suspect most will just want to enable it across the board and having to
> have "compression=allowed" or whatever added to every hba line seems
> likely to be annoying. Maybe a global GUC and then allow the hba to
> override?
Ewe, I would like to avoid going in the GUC & pg_hba.conf direction,
unless we have other cases where we already do this.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, sfrost@snowman.net, pryzby@telsasoft.com, usernamedt@yandex-team.ru, pgsql-hackers@lists.postgresql.org
Subject: Re: libpq compression (part 2)
In-Reply-To: <YdisEaJaBENLmOti@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox