BUG #17247: How to avoid crating multiple Foreign keys on same column on same table. - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17247: How to avoid crating multiple Foreign keys on same column on same table.
Date
Msg-id 17247-dcd5bfeb3d7ecef5@postgresql.org
Whole thread Raw
Responses Re: BUG #17247: How to avoid crating multiple Foreign keys on same column on same table.  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17247
Logged by:          bipsy Nair
Email address:      nbipin29@gmail.com
PostgreSQL version: 13.4
Operating system:   Any OS
Description:

Issue: Postgres engine allows multiple FK on same columns for a same
table.This cause duplication and unwanted use of space . If we accidentally
run a script multiple times it creates the FK mulitple times. 
Ran the following statement 3 times : to add a foreign key
ALTER TABLE admin.emp
ADD FOREIGN KEY (deptno) 
REFERENCES admin.dept (deptno)
ON DELETE NO ACTION;

I see 3 its created thrice . In Oracle this statement should fail. Is there
any way this restriction can be applied on PG. 
admin    emp_deptno_fkey    emp    deptno    admin    dept    deptno
admin    emp_deptno_fkey1    emp    deptno    admin    dept    deptno
admin    emp_deptno_fkey2    emp    deptno    admin    dept    deptno

Please advice.


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17229: Segmentation Fault after upgrading to version 13
Next
From: Noah Misch
Date:
Subject: Re: conchuela timeouts since 2021-10-09 system upgrade