Re: generated constraint name - Mailing list pgsql-docs

From Peter Eisentraut
Subject Re: generated constraint name
Date
Msg-id 8fd70ac1-9eb2-49bf-bdb4-dd2b12beb25e@eisentraut.org
Whole thread Raw
In response to Re: generated constraint name  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: generated constraint name
List pgsql-docs
On 07.04.25 15:34, David G. Johnston wrote:
> On Sunday, April 6, 2025, PG Doc comments form <noreply@postgresql.org 
> <mailto:noreply@postgresql.org>> wrote:
> 
>     The following documentation comment has been logged on the website:
> 
>     Page: https://www.postgresql.org/docs/17/ddl-alter.html <https://
>     www.postgresql.org/docs/17/ddl-alter.html>
>     Description:
> 
>     url:
>     https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-
>     REMOVING-A-CONSTRAINT <https://www.postgresql.org/docs/current/ddl-
>     alter.html#DDL-ALTER-REMOVING-A-CONSTRAINT>
> 
>     (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.)
> 
>     If I have a constraint with the name $2, are there other constraints
>     with
>     names $1, $3 ... ?
> 
> 
> I feel like that whole parenthetical should just go away.  The point of 
> the comment is to remind the user of how identifier values work with 
> respect to mandatory double quoting.  The name itself, other than having 
> a $, has no special importance.

I think generated constraint names were generally "$1", "$2", etc. at 
some point, instead of the more readable ones you get today.  But this 
must be ancient.




pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible documentation inaccuracy in optimizer README
Next
From: Tom Lane
Date:
Subject: Re: generated constraint name