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 1iAP5y-0001sn-T4 for pgsql-docs@arkaria.postgresql.org; Wed, 18 Sep 2019 01:49:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iAP5w-0005M2-HX for pgsql-docs@arkaria.postgresql.org; Wed, 18 Sep 2019 01:49:24 +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 1iAP5w-0005Lu-9t for pgsql-docs@lists.postgresql.org; Wed, 18 Sep 2019 01:49:24 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iAP5t-00034D-Nz for pgsql-docs@lists.postgresql.org; Wed, 18 Sep 2019 01:49:23 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 6B1DE4FA; Tue, 17 Sep 2019 21:49:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 17 Sep 2019 21:49:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=8odzxKa9WzY42MqCtaLI574PlGP vjGJgU62gxxw7bLk=; b=b45uNWEwX2ag1DgcKPtxZ3f8z7lachmAuihUNx5T9ID XAhsSeBffL+FZjayak8wxZF2e8iEs/d7zfk4nRgeczoSsPvnnu3KUs5N0Dq7R9G7 uBd+lVuh5LC3ZFbyxXLyp0s8SiSm0MN/Iwd8qW+n50Qw7OBIAPn4oMPDX7NmO5aH BWROElZ7aXAuUY0HKyPz14WVGu7rXyQ5BjP0iR+H9OPZWG4UM8hn1NtpseR/Xaaf 3Y0FsUFFuULnSFDTruBPreXSiM3Wi3M/tnde3/vttMpz4e005Nt909uGfe8h8/XP 4ETBX8qRbPF/Vg/YXsET1GTDIsUcsjo4bot1a/SzF+A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=8odzxK a9WzY42MqCtaLI574PlGPvjGJgU62gxxw7bLk=; b=zJ8qZhdmtTHJWZFvpkJlZa wxznJYLi/YrB8LOjCP+i+HhlHmVQy5HIfSxdFMt4C/qklOSujmEyBGNjfY417GLR JU4fM9+26obtEpSr/GodJ4bl8SDc2chenEcSnCLp55+LHsfyOUx2VODMXA5LTlqc wvFDXmmU46Hn/PNKqdSm2r93tlwtGLYqrwezDDYWx8GHuEgiwNycgGZVxfBafpgW lf8H2eGZSdMCUUfEzFKJL3NsToKHsQyOoKG6LFgZf4myZPUZsONhOah2XDhp0XLx FSxZJubY/r8FeYaM9IsGPErx2Xpzs6K8V2Zz5BXhY+YucpUaSunPf3yxKOezi1Fw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejgdehvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecukfhppeduuddurddutd dvrddukedtrddukeehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehp rghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd 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 44321D60057; Tue, 17 Sep 2019 21:49:17 -0400 (EDT) Date: Wed, 18 Sep 2019 10:49:14 +0900 From: Michael Paquier To: egashira.yusuke@jp.fujitsu.com, pgsql-docs@lists.postgresql.org Subject: Re: Is it typo of connection_name? Message-ID: <20190918014914.GJ8909@paquier.xyz> References: <156870956796.1259.11456186889345212399@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ucfHZChuBC0NsER/" Content-Disposition: inline In-Reply-To: <156870956796.1259.11456186889345212399@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --ucfHZChuBC0NsER/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 17, 2019 at 08:39:27AM +0000, PG Doc comments form wrote: > The "connection_name" parameter's explanation is not in Parameters > section. > Instead of it, "connection_object" parameter is in Parameters section. Its > explanation seems about "connection_name". > Is it typo about "connection_name" in Synopsis section, or > "connection_object" in Parameters section? Good catch. If you look at the code (ecpg.trailer), connection_object refers to the name of the parameter, while connection_name refers to "AS connection_object" as a whole. So it seems to me that the intention is to use connection_object in the synopsis of the docs. Any thoughts from others? -- Michael --ucfHZChuBC0NsER/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl2BjRoACgkQnvQgOdby QH1sFw//S0/oLysSeIWcTh1F0Jfxr+l2nvH1mDCFABvbSO+E75F8AjttVvsYLPhF Uis+OjfwTvrn6mT8ffX6hcmNRQhXQqCoxswl1Bl0pzCEq4aao5/e14Vsv7oyUuRd lMp28PN7VbB0BM+ggvH/9yZuIvRLg37p/Nzqiq7OYoUj2dOOcdEfmc3G//LxndK0 S0V051UVIgV+DVyjDcq9tuKB5ll7gjDDPttO44lYXcthDTJqYwSAjuxlOp+A1KIP WwBFKsO2co9Mg1oIUrnwBSGZVR43MbT+gJEO+HUJgiH5bB4EkUf6eFZUruIXaHHq ENutSEMpLIdEoawVA+WnLbYaMG6yuv/m8KU1bjOml3QuV5HiehSCuCMyZE5wDdSi DuIem9GCqj2g3tESDd+45bkiXd6FVczvAoqVZzXHvQgFi3E70UhH3Rw26mTm2ezw Finsd8vUaIpLor6Kumb/W91FJFOg2hyWukGdXltxlBuWcMXUmoAy8XAfgTkeVmT3 F4jYmM0gT9Htbu7jPC+qXmCle8s4PJS+mwfRnVXAIIBqUoRbL2tpKNY68VasBtD5 2+n7gTrVyMkPK+n1to/XbnMKaSAuGAnK7yHDdB6c+JDcMvfa0Ypj/b4RIgEBU1Fd zCZa3y1eT3YupkLzbiNZKpZsJElKipWFJrf8MumGlbr4D1v16K8= =ll+I -----END PGP SIGNATURE----- --ucfHZChuBC0NsER/--