Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fQ6Lt-0006x6-5K for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Jun 2018 07:25:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fQ6Lr-0008G8-Ao for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Jun 2018 07:25:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fQ6GY-0008S1-Al for pgsql-hackers@lists.postgresql.org; Tue, 05 Jun 2018 07:20:26 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fQ66E-0005aN-NG for pgsql-hackers@lists.postgresql.org; Tue, 05 Jun 2018 07:09:59 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4478C21D1F; Tue, 5 Jun 2018 03:09:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 05 Jun 2018 03:09:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=ija22unpZxH67iT/UU0G3N3+XGMNWHPxrw4IZI0UvLg=; b=GMmDZPFp 8Rej/TI21DEyEl5YzWwIRCna8RamcMZYwiCxh90lX9l8rrzUGvsWy9lAytj7O/uk Np3L2N2xEv/O1ZoTq+EAKHAE1JKTbJ3CeBndAG6o/wh2kB/ZH6C87R1J04a3j3I8 1vNbm6/yA00ZO2WuNGRi4G36Gtdpdf95wnSt9+9EBX89lbTAu9/M1nqNC1SYRqS8 kiV6MGEi0RmUJq7A2osx67dNqzVuXueSe5ZfhAhtLECydkgb2T8SvbCcdJCL4/WX pLiRJdZdaLwC1AG0BMW8E5TNa5tyLXh0TcdIVib51NZv5OezAVNP2aylpcZNa+Kk oTRj+WokHSHlDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=ija22unpZxH67iT/UU0G3N3+XGMNW HPxrw4IZI0UvLg=; b=Yy2Vt3UdXd3+kCa3hcMR4QA6z/gkNW8V2FWPtIo76VC4v ludb8jz1uc9UpCOYyPvTyWJjHUeke2pYzQVbCSPz8xYXTpLJ5+FJDxwkmTdeOQFx TQuDfjNpIHeInoJkvxftIWWVH2Hiw8U3lz+S6NcpEtKdcKCf1tKlyxst453JmDAz R4dCtR5IU5rmRu88rsrHfWFIPjfgJOii4S27siZ7xIbF4KHpWpNAVapXFN+JVpRD YBjZZqvCak+KIw60LOTDgoyWS7xdOYzzj0H966r1nDq++DzwP8jOExnjJS5t0v0N unDxVoIWEtnjReccB2RWE7xg9r0NKKqXZkzM09YTw== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 7AA8CE443C; Tue, 5 Jun 2018 03:09:36 -0400 (EDT) Date: Tue, 5 Jun 2018 16:09:28 +0900 From: Michael Paquier To: Thomas Munro Cc: Konstantin Knizhnik , Grigory Smolkin , PostgreSQL Hackers Subject: Re: libpq compression Message-ID: <20180605070928.GA4973@paquier.xyz> References: <429cf55b-a8bf-c4ba-196d-5b45420145a1@postgrespro.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 05, 2018 at 06:04:21PM +1200, Thomas Munro wrote: > On Thu, May 17, 2018 at 3:54 AM, Konstantin Knizhnik > Speaking of configuration, are you planning to support multiple > compression libraries at the same time? It looks like the current > patch implicitly requires client and server to use the same configure > option, without any attempt to detect or negotiate. Do I guess > correctly that a library mismatch would produce an incomprehensible > corrupt stream message? I just had a quick look at this patch, lured by the smell of your latest messages... And it seems to me that this patch needs a heavy amount of work as presented. There are a couple of things which are not really nice, like forcing the presentation of the compression option in the startup packet to begin with. The high-jacking around secure_read() is not nice either as it is aimed at being a rather high-level API on top of the method used with the backend. On top of adding some documentation, I think that you could get some inspiration from the recent GSSAPI encription patch which has been submitted again for v12 cycle, which has spent a large amount of time designing its set of options. -- Michael --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlsWNygACgkQnvQgOdby QH053w/+IzxxMxdveeewNbg1iX5S3mRQt/YQPXR3h++8pPJD1duGK8T2ztt65hAt 2x2rLks9xB4gtvEEjcnSA2glCgJnHce1taUp0h6taMydMZt/7Q1rHz+7qEaYBYT3 /FIGgBvTOjq0LyVy4xdAE3cefJK5S1JGjXGSHrNPMMoj/M7MBORbOQz6DvWS7U9O vZoSHCcuGa/+6dv4oeGAvMehrAEsxAAqDizrrTroVvFz8D3/To10PJQQjuoISb53 bQe2gLaAqQPtnlcb4qbOw0fPD4Tt85BBAF6AiwoiHtfh1/OYp3zAJbnur89yxTVy 0p9w0O4blC8elYhZHOWX36OV73k7SkNG10xXWty+J6x8Je82ECQ9nk4zboDAt06H kk/1swHhAup0OeyGSfwcTV/LixPyuO2VXxkJgWuSix1mWe8KTdVzdF3IqRRnWiSR NQKXn+aODdRMHZ6HJay0gfhVNL9C6MOhUZ7U764pmBjn7GCpIVHCOTvLJ7VEXizL 2h81Xuib313pZoOSaqN2OfgeBrmuh7qj8uBZtEEwd99kD678az6+LBS5Sad+B+IQ LeLF5KolHVx9hoXm21nwohBA6hlw6QTtlXYO3NE4Mj/lE1tp92ci6ENpotzqdqRF ZBfoVw2r3rdQXmSFNmJwpOZktGxQ94W/K1/eAJu4ZbT0ln71eqg= =+i+U -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--