From 95e83859b94eca33d3b236c8c8de9e81513e4a12 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 10 Apr 2025 14:49:10 -0400 Subject: [PATCH] Doc: remove long-obsolete advice about generated constraint names. It's been twenty years since we generated constraint names that look like "$N". So this advice about double-quoting such names is well past its sell-by date, and now it merely seems confusing. Reported-by: Yaroslav Saburov Author: "David G. Johnston" Discussion: https://postgr.es/m/174393459040.678.17810152410419444783@wrigleys.postgresql.org Backpatch-through: 13 --- doc/src/sgml/ddl.sgml | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index 5c98f4e2a3d..2333d8ef871 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1470,9 +1470,6 @@ ALTER TABLE products ALTER COLUMN product_no SET NOT NULL; ALTER TABLE products DROP CONSTRAINT some_name; - (If you are dealing with a generated constraint name like $2, - don't forget that you'll need to double-quote it to make it a valid - identifier.)