| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Marcelo Fernandes <marcefern7(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Dominique Devienne <ddevienne(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Best Approach for Swapping a Table with its Copy |
| Date: | 2025-02-14 15:14:45 |
| Message-ID: | CAKAnmm+XYQB71q8=x169XH0ujWsW6wxhZ-h1rZnwjyBPOa18jQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Feb 14, 2025 at 12:41 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-02-14 15:19:57 | Re: Best Approach for Swapping a Table with its Copy |
| Previous Message | Greg Sabino Mullane | 2025-02-14 15:11:48 | Re: Best Approach for Swapping a Table with its Copy |