Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.200.110.1.12\))
Subject: Re: Disable unique constraint in Postgres
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CAAo1mbmvoxTcPdBXdAtZ4oPT-kAOouUpKeYDbqbUsJdFc0CsbA@mail.gmail.com>
Date: Sun, 27 Nov 2022 09:58:54 -0700
Cc: Nikhil Ingale <niks.bgm@gmail.com>,
 pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7F0896B-C1E1-4858-9CC6-A9FAD31727CC@elevated-dev.com>
References: 
 <CALXkTpyQXcT5m7cYttWjLv3n8xGC+MFYVah-q9Lxz-8FKBoMmg@mail.gmail.com>
 <CAAo1mbmvoxTcPdBXdAtZ4oPT-kAOouUpKeYDbqbUsJdFc0CsbA@mail.gmail.com>
To: Samed YILDIRIM <samed@reddoc.net>
Archived-At: 
 <https://www.postgresql.org/message-id/B7F0896B-C1E1-4858-9CC6-A9FAD31727CC%40elevated-dev.com>
Precedence: bulk

> On Nov 27, 2022, at 9:51 AM, Samed YILDIRIM <samed@reddoc.net> wrote:
>=20
> Important point is why you want to disable a unique constraint.=20
>     =E2=80=A2 If you want to add some duplicate rows into a table, you =
try to do something fundamentally wrong.

Even more so: why is disabling superior to dropping???

It is at most an extremely minor convenience to be able to re-enable it =
without having to re-create it, in that you can, presumably, just =
re-enable by name without specifying the constraint details. In other =
words, in my opinion, it is a virtually worthless feature. (Typical =
"enterprise software" feature creep.)