When creating a table in PostgreSQL, default constraint names will assigned if not provided:
CREATE TABLE example (
a integer,
b integer,
UNIQUE (a, b)
);
But using ALTER TABLE to add a constraint it seems a name is mandatory:
ALTER TABLE example ADD CONSTRAINT my_explicit_constraint_name UNIQUE (a, b);
This has caused some naming inconsistencies on projects I've worked on, and prompts the following questions:
Is there a simple way to add a constraint to an extant table with the name it would have received if added during table creation?
If not, should default names be avoided altogether to prevent inconsistencies?
The manual is pretty clear about this ("tableconstraint: This form adds a new constraint to a table using the same syntax as CREATE TABLE.")
So you can simply run:
ALTER TABLE example ADD UNIQUE (a, b);
The standard names for indexes in PostgreSQL are:
{tablename}_{columnname(s)}_{suffix}
where the suffix is one of the following:
pkeyfor a Primary Key constraintkeyfor a Unique constraintexclfor an Exclusion constraintidxfor any other kind of indexfkeyfor a Foreign keycheckfor a Check constraint
Standard suffix for sequences is
seqfor all sequences
Proof of your UNIQUE-constraint:
NOTICE: CREATE TABLE / UNIQUE will create implicit index "example_a_b_key" for table "example"
来源:https://stackoverflow.com/questions/4107915/postgresql-default-constraint-names