Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sYPvI-00BCXC-62 for pgsql-docs@arkaria.postgresql.org; Mon, 29 Jul 2024 12:56:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sYPvF-00HXcU-Eb for pgsql-docs@arkaria.postgresql.org; Mon, 29 Jul 2024 12:56:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sYPvF-00HXar-06 for pgsql-docs@lists.postgresql.org; Mon, 29 Jul 2024 12:56:17 +0000 Received: from mout-u-107.mailbox.org ([80.241.59.207]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sYPvB-0024MX-JH for pgsql-docs@lists.postgresql.org; Mon, 29 Jul 2024 12:56:16 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [10.196.197.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4WXddh5PgSz9sxf; Mon, 29 Jul 2024 14:56:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1722257768; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OoEs+IX3n/i00DQIpqbwj0Q2mcVQS+A2PywHlatzmuw=; b=VI7iPo6t7cRND5pNtoh51otTmOV95Nz7oUaEI/tiFJ281ZVzRA7oMUvemSuZLQ+EcMKnCL hw+FfqG7DHG7IdwMO3gPrLdgc7m312Pt3yVRRPkwuL2Zj/DXJcYOqwIN0CMeMqNg31Qoja OiYoUqVGdhWZy3GjH0T5LPTUUPSLUNBxVEepbl0iO2tKOsL0Z3R99fENLo2Q7aJqilLhho LJeriCCOb7wxsquo9dlqSEevsAe7l0Zs2YD0cu97zrrVAkiYKF+10auESfrPTOF7kRT1jj vb5devfiVdmkOW0rSxvhDjb5U51Q3FxhUCgL3RuwEt6X3aC+k+OIedxDbVrYSg== Date: Mon, 29 Jul 2024 14:56:05 +0200 From: Erik Wienhold To: elionescu@yahoo.com, pgsql-docs@lists.postgresql.org Subject: Re: incorrect (incomplete) description for "alter domain" Message-ID: References: <172225092461.915373.6103973717483380183@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <172225092461.915373.6103973717483380183@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-07-29 13:02 +0200, PG Doc comments form wrote: > In the Synopsis section of > https://www.postgresql.org/docs/current/sql-alterdomain.html > this is incorrect (incomplete): > "ALTER DOMAIN name ADD domain_constraint [ NOT VALID ]" > It should be > "ALTER DOMAIN name ADD CONSTRAINT domain_constraint [ NOT VALID ]" No, the docs are correct. domain_constraint refers to this syntax defined by CREATE DOMAIN: "where constraint is: [ CONSTRAINT constraint_name ] { NOT NULL | NULL | CHECK (expression) }" Also, PG 17 renames this to "domain_constraint" with commit 9895b35cb8 to align ALTER DOMAIN with CREATE DOMAIN. -- Erik