MIME-Version: 1.0
References: <CAM2F1VP9nn0F6fSjbmhJCNSjv-dbAJcAytZ2HkTkZ0dGYZvxrw@mail.gmail.com>
 <8ac6a1dd-db82-4ea7-8186-0c354d79049f@aklaver.com> <CAM2F1VOOn1izCrtcrDx4YUtCY-H64Vj5yvN5H1Lhk8kCY+_W6Q@mail.gmail.com>
 <44BB6A74-0AB1-462C-B13A-2CF106DA70D6@kleczek.org>
In-Reply-To: <44BB6A74-0AB1-462C-B13A-2CF106DA70D6@kleczek.org>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 14 Feb 2025 10:19:57 -0500
Message-ID: <CAKAnmmLcD9y9WMTNCuPfhGOW17KS-+9kKo44Ve85CHu+YJ8WCA@mail.gmail.com>
Subject: Re: Best Approach for Swapping a Table with its Copy
To: =?UTF-8?B?TWljaGHFgiBLxYJlY3plaw==?= <michal@kleczek.org>
Cc: Marcelo Fernandes <marcefern7@gmail.com>, Adrian Klaver <adrian.klaver@aklaver.com>, 
	pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000052736a062e1bb767"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLcD9y9WMTNCuPfhGOW17KS-%2B9kKo44Ve85CHu%2BYJ8WCA%40mail.gmail.com>
Precedence: bulk

--00000000000052736a062e1bb767
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 14, 2025 at 1:02=E2=80=AFAM Micha=C5=82 K=C5=82eczek <michal@kl=
eczek.org> wrote:

> Create index concurrently and then fiddle with the catalog tables to
> define the constraint using this index?
>

You mean an ALTER TABLE ... ADD CONSTRAINT ... EXCLUDE without actually
doing an ALTER TABLE. Nope, that's far worse than the pg_repack
shenanigans, as we would be creating new catalog objects.

Ideally would be that someone adds support for USING INDEX for an exclusion
constraint.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

--00000000000052736a062e1bb767
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Feb 14, 2025 at 1:02=E2=80=AFAM M=
icha=C5=82 K=C5=82eczek &lt;<a href=3D"mailto:michal@kleczek.org">michal@kl=
eczek.org</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_contain=
er"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">Create index concurre=
ntly and then fiddle with the catalog tables to define the constraint using=
 this index?<br></blockquote><div><br></div><div>You mean an ALTER TABLE ..=
. ADD CONSTRAINT ... EXCLUDE without actually doing an ALTER TABLE. Nope, t=
hat&#39;s far worse than the pg_repack shenanigans, as we would be creating=
 new catalog objects.</div><div><br></div><div>Ideally would be that someon=
e adds support for USING INDEX for an exclusion constraint.=C2=A0</div><div=
><br></div><div>Cheers,</div><div>Greg</div><div><br></div><div>--</div></d=
iv><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><div>Crunchy=
 Data - <a href=3D"https://www.crunchydata.com" target=3D"_blank">https://w=
ww.crunchydata.com</a></div><div>Enterprise Postgres Software Products &amp=
; Tech Support</div><div><br></div></div></div></div>

--00000000000052736a062e1bb767--