Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isL8s-0006Wn-Cj for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Jan 2020 06:30:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1isL8p-0000eN-M5 for pgsql-bugs@arkaria.postgresql.org; Fri, 17 Jan 2020 06:29:59 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isL8p-0000eG-Dr for pgsql-bugs@lists.postgresql.org; Fri, 17 Jan 2020 06:29:59 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1isL8i-0001DV-84 for pgsql-bugs@lists.postgresql.org; Fri, 17 Jan 2020 06:29:58 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DBDCB21F85; Fri, 17 Jan 2020 01:29:50 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 17 Jan 2020 01:29:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=mCgczQXs3yi0cYC1InEb0LPr9J7 GLsllDIUKibTU8ro=; b=aWAaqBNOgziLqSMizbXeVZ9M//yW6WiEIaNqyWM9EBS 0NIKoSFBL/CaVeAEOVeEz91rIdYJc8GH9zpMNfSsbPHSECl5lLmHk/7ab29e8CN6 0otHdB5hslaf6+BOF8UZnc/vDTsmNmelQG/Xm3sMMeuZUyz86gdGdI7cPTJp7Kdf jUreNmu7S0BlkwBm1gX6sSY1+AyaAZHqv6HhA3/TqRfq5Nn9IXYYxx3o2Cg0ziQ0 9wps8nyB48D2M1t9ehncHD5UWt4/0Io8bB4lxY6gEa91cP+WQSvNsKT+AsfazICn 7mz4bn+/gNIhMWEDefkPBJJhs+Q3e1MlWSsHLARJIwA== 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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=mCgczQ Xs3yi0cYC1InEb0LPr9J7GLsllDIUKibTU8ro=; b=KhsNJeHDC3HXLUmvhgBAFx RO3XLUnIq7uKsUfnBHy+7c22VmKjQBaTiGi9+MI/ysFlD4Tl5TyO7xvs6As0iMm5 et4rNpI8J/2p9tVoNrDj44xK0vXxGgT4tD/44mpZJi46LzmBihL95HxDLXsbw/4N NyehXn1RMIJGMFuLHb/K/V3PuCH9334sa6GA0XGqe/UsGWSPDum8tbS+mRi2PXUx CW2bO14hG9+xD06zT1NoTWwvoGFsfAwU/Q/ewd/J6gI7+x0dH7elnqf3tRGwtYY1 DV0arcB0m7um1+TuDrFJds4PCHKLXaDd7abpn8lQ4T+82TsvBo8NdiTF4Ksi9aRw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrtdeigdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecukfhppeduuddurddutddvrddukedtrddukeehnecurfgrrhgr mhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluh hsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id BBD9330609DC; Fri, 17 Jan 2020 01:29:48 -0500 (EST) Date: Fri, 17 Jan 2020 15:29:45 +0900 From: Michael Paquier To: Oleksandr Shulgin Cc: Peter Eisentraut , Jobin Augustine , Heikki Linnakangas , pgsql-bugs@lists.postgresql.org Subject: Re: libpq parameter parsing problem Message-ID: <20200117062945.GJ2127@paquier.xyz> References: <22b4a79a-5d60-cec0-474e-4a68c8be2b7a@iki.fi> <20200109043809.GK2251@paquier.xyz> <20200114060317.GF1515@paquier.xyz> <20200116034917.GD3117@paquier.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="x0KprKst+ZOYEj2z" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --x0KprKst+ZOYEj2z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 16, 2020 at 09:17:23AM +0100, Oleksandr Shulgin wrote: > At the same time, we could still be more specific if we would say > "delimiters" instead of the generic "special meaning". Should we then > provide an exhaustive list of delimiters or is it clear enough like that? > For example, the whitespace doesn't need to be percent-encoded (it doesn't > hurt as you might be able to spare the quoting if using it as an argument > to a shell command), while the "equal sign", when used in the query string > part, does need encoding. This term comes from you, as of 2d612ab, and that does not look like something to change because reserved characters have "sometimes" a special meaning in this context. A reference to the RFC is sufficient IMO, readers could always look at that reference for a precise list and that would bloat the docs more than necessary. -- Michael --x0KprKst+ZOYEj2z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4hVFkACgkQnvQgOdby QH0n9w//Xmk/Uhuhxr93GD7bihzQR1x2le7uf3mqAGqtuwNJTmD9VCEq0eKrx4Dl FNxFbyyZIb2LvqevMJb+OI2tJIe0QCGLbg4kksradv/SGora21fvyNj63+BKMjLU H1RFRYLSL7Z01XB+tYIK+dtgiB7J90TxOBSYItNuo5MtjGVuAg9AMV6mhycx2br1 5c4fZfei3TmLqQkLGQM27T6himYN3csg8076V6UUuFYvd4AiNNFfCulLoCJ4dlRz wJwWofkLWRpebJvyuVIl7Zma7eJq7Fn9M32dOaSelBEty7Che9dWEwKydmg9SR6m mxn0EfJeEbSLAvaiE01daaDRKZrONpQIUimCxO5bDQNEUF7HjMHO3Ithai3UxZzE ltv/vr1sc3nJ6mzLI1yewedE3/bJqHr9sesxGWknW7hrzQiOUJMELq8Y9zXq06o3 JElnihT/pkZb07vFyHoNHFYGXl3kfvUpteP2hJCXkhXEmsN90/3FuJMuY8ou9nBC SgA5KEmsLgqTtdp8yHlkfRr5RzrXXnXn8z0VMrMhN7Cij7nkMperXW0TImmAg6eL gAAbqkVAqkqkgRh3vZjU5FMtXzMMHoAu4MdXkfym47CQZjCeCNqkq/nr2PBxPBFA cejz2uGDrAkqUE5PG/BfyH/E1uY6BSdSX/jCGrpWZ2dX1tsL0No= =WEtk -----END PGP SIGNATURE----- --x0KprKst+ZOYEj2z--