MIME-Version: 1.0
References: <CAM2F1VP9nn0F6fSjbmhJCNSjv-dbAJcAytZ2HkTkZ0dGYZvxrw@mail.gmail.com>
 <8ac6a1dd-db82-4ea7-8186-0c354d79049f@aklaver.com> <CAM2F1VOOn1izCrtcrDx4YUtCY-H64Vj5yvN5H1Lhk8kCY+_W6Q@mail.gmail.com>
 <9fa75099-1ee9-43de-ac6e-945841b184eb@aklaver.com> <CAM2F1VONo8M9gcybhmf8-CdmRUC2QrFGZkZLYF-+uLZuhRKaxQ@mail.gmail.com>
 <22406cdf-83f5-4b98-b07e-7827afe97f93@aklaver.com> <CAM2F1VMdDSxLhccn=0pXriJrR6a7Oe9Kir1DB_0pW1v88bsvCg@mail.gmail.com>
 <CAKAnmmJ04kH_gWR+cOFWD0h63RDck1k6hqQYH8K30-cfCvtO_Q@mail.gmail.com>
 <CAFCRh-9xC0CXKM2GTQBfjYY5GQx29Uit+fY5PpBFTvX927YC8w@mail.gmail.com>
 <94e1205e-8ddf-403b-8477-02d7939f2905@aklaver.com> <CAM2F1VMApyPvdA4ERoF7Fob6CXimgOWMKC1vayO5OQa3TtJAFQ@mail.gmail.com>
 <ebdbbe8d0b905e797d4bb10157e44f9fe6ecb389.camel@cybertec.at>
In-Reply-To: <ebdbbe8d0b905e797d4bb10157e44f9fe6ecb389.camel@cybertec.at>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 14 Feb 2025 10:14:45 -0500
Message-ID: <CAKAnmm+XYQB71q8=x169XH0ujWsW6wxhZ-h1rZnwjyBPOa18jQ@mail.gmail.com>
Subject: Re: Best Approach for Swapping a Table with its Copy
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Marcelo Fernandes <marcefern7@gmail.com>, Adrian Klaver <adrian.klaver@aklaver.com>, 
	Dominique Devienne <ddevienne@gmail.com>, pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a92ec0062e1ba45f"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BXYQB71q8%3Dx169XH0ujWsW6wxhZ-h1rZnwjyBPOa18jQ%40mail.gmail.com>
Precedence: bulk

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

On Fri, Feb 14, 2025 at 12:41=E2=80=AFAM Laurenz Albe <laurenz.albe@cyberte=
c.at>
wrote:

> Moreover, you have to make sure to send out invalidation messages so that
> every session that caches statistics or
> execution plans for the tables discards them.


Hmm...is that really necessary? Because if so, there is no direct SQL-level
way to do that I am aware of, so we are back to a C extension. Or just
restarting the cluster :)

Cheers,
Greg

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

--000000000000a92ec0062e1ba45f
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 12:41=E2=80=AFAM =
Laurenz Albe &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">laurenz.albe@c=
ybertec.at</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_contai=
ner"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">Moreover, you have t=
o make sure to send out invalidation messages so that every session that ca=
ches statistics or<br>
execution plans for the tables discards them.</blockquote><div><br></div><d=
iv>Hmm...is that really necessary? Because if so, there is no direct SQL-le=
vel way to do that I am aware of, so we are back to a C extension. Or just =
restarting the cluster :)</div><div><br></div><div>Cheers,</div><div>Greg</=
div><div><br></div></div><div dir=3D"ltr" class=3D"gmail_signature"><div di=
r=3D"ltr"><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchyda=
ta.com" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterpr=
ise Postgres Software Products &amp; Tech Support</div><div><br></div></div=
></div></div>

--000000000000a92ec0062e1ba45f--