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.96) (envelope-from ) id 1x5PFJ-0003ET-35 for pgsql-docs@arkaria.postgresql.org; Sat, 12 Sep 2026 15:02:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x5PFJ-001Ezx-1F for pgsql-docs@arkaria.postgresql.org; Sat, 12 Sep 2026 15:02:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x56dT-0005r0-0t for pgsql-docs@lists.postgresql.org; Fri, 11 Sep 2026 19:10:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x56dQ-00000005Bc5-3YFo for pgsql-docs@lists.postgresql.org; Fri, 11 Sep 2026 19:10:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=pvk2etZaxaehfZL7KF/eBieNFXupySvQ1gxbTx/6lcg=; b=4nFWdaF/xzw+4LE2TFeRmNrMNH 0zFnk+4fw2avqvzb4cAzznMasm0WmGGIytQbmDRQiM539GdXmQgTQc4QcPoPQvXvRMhInMZO8PRC0 qBlp2gzoLKajaXrAiJO6XW3IxItdPEHKbeh6IdbmzuZcWhBD66qlFwXKZrDTk3Bd6GcgLvi+sPMjr 6xepIesoVhGJEt2Db31PTlDhwOr0CbBbSkAA8m5CyoXeNPlTOPLdLmhbsQN0XbyxkjsMSaNi64w0s 6CdfgPuF2Gln8jGbvsInkLbDqGzPvxFNjjOt9M0N3dykqk0Yz1AQalpskgoO5JZGIVAmIo+YQNxsB WLvBb0hw==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x56dQ-00FVaG-1e for pgsql-docs@lists.postgresql.org; Fri, 11 Sep 2026 19:10:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x56dP-00000006RPb-0C6j for pgsql-docs@lists.postgresql.org; Fri, 11 Sep 2026 19:10:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Constraint check is missing value check ARRAY To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: eugene.losowskigallagher@googlemail.com Reply-To: eugene.losowskigallagher@googlemail.com, pgsql-docs@lists.postgresql.org Date: Fri, 11 Sep 2026 19:09:38 +0000 Message-ID: <178915377800.2258529.262291845008098767@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/ddl-constraints.html Description: Hi Documentation team This page is missing the value check array. https://www.postgresql.org/docs/current/ddl-constraints.html Example: CREATE TABLE demo ( id bigint NOT NULL DEFAULT nextval('seq_ttelephone_id'::regclass), usage character(1) NOT NULL DEFAULT 'M', CONSTRAINT ck_ttelephone_usage_1 CHECK (usage =3D ANY (ARRAY['M'::character(1),'H'::character(1),'W'::character(1),'F'::character= (1)])) NOT VALID ) ); This is entirely missing from the documentation. Key thing to point out is the type cast must match: e.g. character(1) for type of character(1) etc Please add this to the documentation, last knowledge on web for this is 10-years old, and this is a current feature of postgres (using 17.11 currently) Many thanks Eugene