pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Dropping behavior for unique CONSTRAINTs
Date: Fri, 3 Mar 2023 15:55:24 -0600
Message-ID: <60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com> (raw)
In-Reply-To: <CAApHDvpTsAUkiakGDzJGxMVG0H1vq=h51+107B6ERe5XfD5T-A@mail.gmail.com>
References: <3d7d49f0-7eef-4d6d-8dc3-1993ba2fc2cb@me.com>
	<CAApHDvpTsAUkiakGDzJGxMVG0H1vq=h51+107B6ERe5XfD5T-A@mail.gmail.com>

On 3/3/23 04:54, David Rowley wrote:
> On Fri, 3 Mar 2023 at 23:17, Conner Bean<conner.bean@icloud.com>  wrote:
> I wanted to avoid using a unique index since dropping them requires an
> exclusive lock and cannot be done concurrently. My thought was to then
> use a unique constraint, since I've read unofficial docs[0] that say
> these can be dropped safely with no lock.
>
> You should try the official documents.  You won't find any wording in
> those that say that a unique constraint can be dropped without any
> locking.
>
> If you look athttps://www.postgresql.org/docs/current/sql-altertable.html
> you'll see "Note that the lock level required may differ for each
> subform. An ACCESS EXCLUSIVE lock is acquired unless explicitly
> noted.", and if you look at DROP CONSTRAINT that it mentions nothing
> about any lower-level locks, so you can assume that DROP CONSTRAINT
> obtains an access exclusive lock on the table being altered.
>
> If you have a look at
> https://www.postgresql.org/docs/15/sql-dropindex.html  check out the
> CONCURRENTLY option. That option allows an index to be dropped without
> blocking concurrent reads and writes to the table. It seems like just
> having a unique index without the constraint is likely your best bet
> if you can't afford to block any traffic for the brief moment it would
> take to drop the constraint.

That doc page says this about CONCURRENTLY:
"
There are several caveats to be aware of when using this option. Only one 
index name can be specified, and the CASCADE option is not supported. (Thus, 
*an index that supports a UNIQUE or PRIMARY KEY constraint cannot be dropped 
this way.*)
"

-- 
Born in Arizona, moved to Babylonia.

view thread (10+ messages)  latest in thread

Message-ID: <60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com>
Permalink:  ../60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com/
Also on:    postgresql.org/message-id/60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Dropping behavior for unique CONSTRAINTs
  In-Reply-To: <60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com>
  References: <3d7d49f0-7eef-4d6d-8dc3-1993ba2fc2cb@me.com> <CAApHDvpTsAUkiakGDzJGxMVG0H1vq=h51+107B6ERe5XfD5T-A@mail.gmail.com> <60c7fb5d-57ba-7c49-affc-e6d1739772a7@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox