From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | michael(at)mibi(dot)io |
Subject: | BUG #15670: alter table .. add column if not exists ... references ...; adds a FK constraint on each execution |
Date: | 2019-03-05 13:52:16 |
Message-ID: | 15670-b9093d589e3cf8db@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15670
Logged by: Michael Binder
Email address: michael(at)mibi(dot)io
PostgreSQL version: 11.2
Operating system: Debian 9.8
Description:
Hi,
I don't know if this is the expected behavior but when I execute this
script:
create table test1 (
id serial primary key,
name text
);
create table test2 (
id serial primary key
);
alter table test2 add column if not exists test1_fk integer not null
references test1(id);
alter table test2 add column if not exists test1_fk integer not null
references test1(id);
alter table test2 add column if not exists test1_fk integer not null
references test1(id);
I end up with 3 FK constrains:
select
constraint_name
from information_schema.key_column_usage
where table_name='test2'
and position_in_unique_constraint is not null;
--
test2_test1_fk_fkey
test2_test1_fk_fkey1
test2_test1_fk_fkey2
best regards,
Michael Binder
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2019-03-05 14:04:17 | Re: BUG #15668: Server crash in transformPartitionRangeBounds |
Previous Message | PG Bug reporting form | 2019-03-05 11:06:00 | BUG #15669: Error with unnest in PG 11 (ERROR: 0A000) |