From: Tom Lane Date: Thu, 10 Apr 2025 18:49:10 +0000 (-0400) Subject: Doc: remove long-obsolete advice about generated constraint names. X-Git-Tag: REL_18_BETA1~176 X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=d89335eea67c1cb55b03d5235320cc107287b59a;p=postgresql.git 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 --- diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index d2082b7e88e..fcd1cb85352 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1764,9 +1764,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.)