Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMu6F-0003OX-GV for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2023 17:07:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMu6E-00037t-EI for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Jan 2023 17:07:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMu6D-000357-IX for pgsql-hackers@lists.postgresql.org; Tue, 31 Jan 2023 17:07:14 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMu6B-0000vK-2l for pgsql-hackers@postgresql.org; Tue, 31 Jan 2023 17:07:13 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 65E225C00C5 for ; Tue, 31 Jan 2023 12:07:09 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 31 Jan 2023 12:07:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ilmari.org; h=cc :content-type:date:date:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to; s=fm3; t= 1675184829; x=1675271229; bh=zTlBnzwOtS2YTtiQzw8hZj6M/p8IPzndETa 8w4WRquQ=; b=s9hcsno0KCA1Py8f+ZDMgB2q9IT7GKgIxCQ1wHrmgvSiA516rUa W0QV6ifbmbIyTRaGC5MnkOgcbaCb00IXBssiiOg/DFnm3hs8sG1VU2x70iYPwBzw f6gQ/1p/feoDP43oaT29297jQnXHAdrQwkBunkon9eVgg3+yhGiAZW/ChrasprzV +0+k6A0aP2TtJ3+Ff7tV/46k7FCCMldddQYCXJ6xKlmzSHIfcFCPtcY+l3g1BvPT G/DysgdqLE4g04HKWAzZ33oenMdu5m0War8PZ7wHx+HqTtb/MuWSVm+UTvqGK6G7 2FB7+bO1KrZya5iqerUerVN29sTHZBgIJMA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1675184829; x= 1675271229; bh=zTlBnzwOtS2YTtiQzw8hZj6M/p8IPzndETa8w4WRquQ=; b=H nGD7ntblYqRPBfy0zYcS00n21VXjpVQGxcvRc9EGy8s4EE0oiN7poVU9mlRizhoH 3ZiIsBWxZiXtEslp2SaflIQ12LwBRrsQWpnThsQx5EVULDC5N7tyq2vutmLb+frJ 3PxGwkpilBmooziQeUdLri5Eg+RczTu5GbRUjvkEp4yAbcHcBPg4XkkxpEg4yjIA ZIdt0xgIIxat8wp3jdTOtCiPBEVPfuXa8oxVVdV0eVEbUKTOJaMWikxOhp4D6E+6 u9wuSU0mSTw3JPb5nJuZp42qZCBHUutPhtmYPtMCV7F9Z8SvtNsDgLAtPyrHKcMe mwEBal/KtdI0/LbLz3Xaw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefgedgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkfgggtgesmhdtreertd erjeenucfhrhhomhepffgrghhfihhnnhcukfhlmhgrrhhiucforghnnhhsnohkvghruceo ihhlmhgrrhhisehilhhmrghrihdrohhrgheqnecuggftrfgrthhtvghrnhepieeiveetvd euveevkeefueejieekgfdvtdetffekgeejtedvjeetheehueeliedvnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepihhlmhgrrhhisehilhhmrg hrihdrohhrgh X-ME-Proxy: Feedback-ID: i1ff147bf:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 31 Jan 2023 12:07:08 -0500 (EST) From: =?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= To: pgsql-hackers@postgresql.org Subject: Clarify deleting comments and security labels in synopsis Date: Tue, 31 Jan 2023 17:07:06 +0000 Message-ID: <87sffqk4zp.fsf@wibble.ilmari.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Hi Hackers, A user on IRC was confused about how to delete a security label using the `SECURITY LABLEL ON … IS …` command, and looking at the docs I can see why. The synopsis just says `IS 'label'`, which implies that it can only be a string. It's not until you read the description for `label` that you see "or `NULL` to drop the security label." I propose making the synopsis say `IS { 'label' | NULL }` to make it clear that it can be NULL as well. The same applies to `COMMENT ON … IS …`, which I've also changed similarly in the attached. - ilmari --=-=-= Content-Type: text/x-diff Content-Disposition: inline; filename=0001-Clarify-that-COMMENT-and-SECURITY-LABEL-can-be-set-t.patch From cb02bd9aae85a48355dede9dd13db809f6ada35b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dagfinn=20Ilmari=20Manns=C3=A5ker?= Date: Tue, 31 Jan 2023 16:05:20 +0000 Subject: [PATCH] Clarify that COMMENT and SECURITY LABEL can be set to NULL in the synopses This was only mentioned in the description of the text/label, which are marked as being in quotes in the synopsis, which can cause confusion (as witnessed on IRC). --- doc/src/sgml/ref/comment.sgml | 2 +- doc/src/sgml/ref/security_label.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/ref/comment.sgml b/doc/src/sgml/ref/comment.sgml index 7499da1d62..f5daea7a7e 100644 --- a/doc/src/sgml/ref/comment.sgml +++ b/doc/src/sgml/ref/comment.sgml @@ -66,7 +66,7 @@ TRIGGER trigger_name ON table_name | TYPE object_name | VIEW object_name -} IS 'text' +} IS { 'text' | NULL } where aggregate_signature is: diff --git a/doc/src/sgml/ref/security_label.sgml b/doc/src/sgml/ref/security_label.sgml index 20a839ff0c..3df5ed2e9c 100644 --- a/doc/src/sgml/ref/security_label.sgml +++ b/doc/src/sgml/ref/security_label.sgml @@ -44,7 +44,7 @@ TABLESPACE object_name | TYPE object_name | VIEW object_name -} IS 'label' +} IS { 'label' | NULL } where aggregate_signature is: -- 2.34.1 --=-=-=--