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 1w93Br-0019Fo-2G for pgsql-docs@arkaria.postgresql.org; Sat, 04 Apr 2026 15:45:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w93Bq-00H8qA-0A for pgsql-docs@arkaria.postgresql.org; Sat, 04 Apr 2026 15:45:38 +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.96) (envelope-from ) id 1w8bl2-00BJbm-0X for pgsql-docs@lists.postgresql.org; Fri, 03 Apr 2026 10:28:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w8bkz-00000000ME0-1DWw for pgsql-docs@lists.postgresql.org; Fri, 03 Apr 2026 10:28:08 +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=1yRTS59QnVloGAanPd3Ds9IR/CdTB3Hl040YeP2hvrA=; b=E+f8P0ONQnZ4LYDkBU62cA1Ii6 Us71vakUjGbLh1l2GbYCiIi2tM6i49ih+zar5hv03KazcMVWMmKkDfm4udOd+hfHus74cbldqQQiW AbtBqSdrJh8Kre4klDTYtpRn7r/XZwVKbTqrslqk3Joi1/r1KquFHC50XB9oXhPjnU2pSlVBOUnP5 DidR+ANdNtB/tWszp+bhH494Vou7tcBw8gwWB6KvNxpgo++GaG2VLYtXDdofii89/YnsUhvO09/Fi zjDINfHS6ueCtTt2UYL0SbKGUO/2Y03g7mPm5u2ykROD2scCsaRY8znfcd9bzEMe5hXiq/gkl3GTD hxTpGD/w==; 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 1w8bky-000wqS-0f for pgsql-docs@lists.postgresql.org; Fri, 03 Apr 2026 10:28:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8bkw-00Ej9t-19 for pgsql-docs@lists.postgresql.org; Fri, 03 Apr 2026 10:28:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: The CREATE TABLE documentation groups NOT NULL under table_constraint. To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: jnishtha305@gmail.com Reply-To: jnishtha305@gmail.com, pgsql-docs@lists.postgresql.org Date: Fri, 03 Apr 2026 10:27:22 +0000 Message-ID: <177521204282.3221089.12751196147738658456@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.html Description: Unlike UNIQUE or CHECK, NOT NULL cannot be used standalone at the table level in a standard way Example: CREATE TABLE t (a int, NOT NULL a); fails. It only works as an "out-of-line" constraint in very specific inheritance scenarios.