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 1g7FJs-0000DH-0k for pgsql-docs@arkaria.postgresql.org; Tue, 02 Oct 2018 07:42:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g7FJp-0001is-Ma for pgsql-docs@arkaria.postgresql.org; Tue, 02 Oct 2018 07:42:09 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7FJh-0001Di-GR for pgsql-docs@lists.postgresql.org; Tue, 02 Oct 2018 07:42:03 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7FJe-00083K-Pa for pgsql-docs@lists.postgresql.org; Tue, 02 Oct 2018 07:42:01 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6B3BF21DCC; Tue, 2 Oct 2018 03:41:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 02 Oct 2018 03:41:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= 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=eCVaZyWgWhxE4cK5MXDBw0GFqMOq2Rvfdjuw1Koza9E=; b=YDig3fry UYa5/W3S+V6Enztbl/um6PGPRdVHu5h9Iiu878uEpzxP3JwoI5gKbGqKcZ0JB5jw H4uvyPiozmFzal6hnJvS3Vx/eGZS4WdgceBh4B71BMox/v1wZNc7mbV5Smuhnftx M/JsgMZDDGcPAPXQoWoB/jxeRVBovNprwcjbgGYIxoX2fdPJj7CgWNt3MUAu9jtH XA+Sh/VmpI8+jHAx2y+wMeLmqDPSf/Ov/StSKbVb9ZiS1KQT31vRD8LSFYmL5v1Y TGtCzK9ukdKFxgsGz+HUaDzfKrFfaGPPQP3Fkoc4eg6VsrcvcYQb8vmtX5uk8e28 uWSWQ04tRqtJqg== 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-sender :x-me-sender:x-sasl-enc; s=fm3; bh=eCVaZyWgWhxE4cK5MXDBw0GFqMOq2 Rvfdjuw1Koza9E=; b=t1Q08ihI0Q+1wrcQlh95m+W/k+AWRgCVHNCt0PdzYd5O/ 3rlXg4HZXyPG3jM0uzSoxDJopbhfG55+9nXIFVDX+U3jxSrIbkmZn98o/kycRBxJ 4geR0UTRV5ut5Hc7Svuk35ebPvAWVPjQGPMaTM/RoyXfEo+XJGLtU4x/yvi/s/jw c3qb3KegTlFDgVTlOQt5inbEW+5zED3Rel/vrVAvxwm+TdxsLSXqQAWSEZF/3HFF V6Hq2GtBMgnuTvN4OzvAzdjv6C1gNnKxJ28hSfijHwbzDrLN8R1eN3qXp6GH8bsB fgf6EfHXGnU2AtgiBi9PrGMfgg3N/xP1L5e/0eOhg== X-ME-Sender: X-ME-Proxy: Received: from paquier.xyz (mp76f1fb95.ap.nuro.jp [118.241.251.149]) by mail.messagingengine.com (Postfix) with ESMTPA id A1033E4118; Tue, 2 Oct 2018 03:41:55 -0400 (EDT) Date: Tue, 2 Oct 2018 16:41:52 +0900 From: Michael Paquier To: chris+postgresql@qwirx.com, pgsql-docs@lists.postgresql.org Subject: Re: pgrowlocks columns do not match docs: "modes" instead of "lock_type" Message-ID: <20181002074152.GD17642@paquier.xyz> References: <153838692816.2950.12001142346234155699@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="+SfteS7bOf3dGlBC" Content-Disposition: inline In-Reply-To: <153838692816.2950.12001142346234155699@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --+SfteS7bOf3dGlBC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 01, 2018 at 09:42:08AM +0000, PG Doc comments form wrote: > The description of the pgrowlocks extension says that the function return= s a > column called "lock_type". However this column is really called "modes", = as > shown in contrib/pgrowlocks/pgrowlocks--1.2.sql: >=20 > CREATE FUNCTION pgrowlocks(IN relname text, > OUT locked_row TID, -- row TID > OUT locker XID, -- locking XID > OUT multi bool, -- multi XID? > OUT xids xid[], -- multi XIDs > OUT modes text[], -- multi XID statuses > OUT pids INTEGER[]) -- locker's process id > RETURNS SETOF record > AS 'MODULE_PATHNAME', 'pgrowlocks' > LANGUAGE C STRICT PARALLEL SAFE; 0ac5ad5 has updated pgrowlocks from 1.0 to 1.1 and it forgot the documentation. The order of the columns is correct, but the example was not. So I updated the documentation with a fresh one, and fixed it all the way down to 9.3. Thanks for the report, Chris! -- Michael --+SfteS7bOf3dGlBC Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAluzIUAACgkQnvQgOdby QH3aGw//fL0fiiP9ORzd2n0VwAaCqKrukTTDIz1R4ayqJ4bOxAnpMAmnOD9Eo1zP 2qaFjMFVJu0CM2+3KwKs+Af4bfcyROhpOZnNyCqGOs8/f+TRjkj9zqkApxusA7Fd CVAbl7JirTp8vn1Sxf2jjRoHcEFZ1JUZzf53/5DSmvUGafcEucbX/eCmwDMpr3PI 1jsHSikHMJgZQ3CJB95RiZzmzSBL1p3FNYAG1Stx+HCxrwwxOP5877MKs3WS9rJX EAXKFrBirJES+fuOHECxRfJrINwMYwaCXunPdOIbXEl5DSHUKNRDz1UvpWY/gtl0 bBiiiEvf/zmqOzA8JN4+VIDGb22Jf7ZdvKvbryCgFQ86ifP+IocG1Pu9ghCdwh0w r4nFWyk/cQn4cxXjNo0BzH9A8GwhtPE+oNiuMApg6RITFnmiM6cXKkOyGOu5uboe gAA4oH/thPPNm5eAaRwzxT29tFNfk2pp72+9ul7gAgKFeTmdMNNrG8JhiKFqvr+h yIYiAwHQz56jcmTFQ8Bk5gVqTiK2+YDIzYKb04l7kwUOTPu0TEhxB9qPPqPAfCuQ YxJM6ZcyDglAcxS8k0Rh/aDSK82BywrH93/4hmdd1Bc2wiUK4zD4y2G62n5edYvM kXUjJfXGlBDoHbPwaLQFi0EYR1WHG/ZiZoYBZXy00ONwbp7oUF4= =sclI -----END PGP SIGNATURE----- --+SfteS7bOf3dGlBC--