| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: teach pg_upgrade to handle in-place tablespaces |
| Date: | 2025-07-22 02:17:42 |
| Message-ID: | aH70xl4GQzrTHpYL@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 21, 2025 at 09:06:59PM -0500, Nathan Bossart wrote:
> On Tue, Jul 22, 2025 at 10:37:05AM +0900, Michael Paquier wrote:
>> This would not choke as long as the old cluster is at least at v10,
>> but well why not.
>
> I'm not sure what you mean. allow_in_place_tablespaces was added in v15,
> right?
Yes initially, not so these days. Here are the backpatches across
v10~14:
<16e7a8fd8e97> 2022-07-27 [Alvaro Herrera] Allow "in place" tablespaces.
<961cab0a5a90> 2022-07-27 [Alvaro Herrera] Allow "in place" tablespaces.
<7bdbbb87340f> 2022-07-27 [Alvaro Herrera] Allow "in place" tablespaces.
<258c896418bf> 2022-07-27 [Alvaro Herrera] Allow "in place" tablespaces.
<ca347f5433ed> 2022-07-27 [Alvaro Herrera] Allow "in place" tablespaces.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-07-22 02:25:27 | Re: [PATCH] Check for TupleTableSlot nullness before dereferencing |
| Previous Message | Peter Smith | 2025-07-22 02:15:18 | Re: Update Examples in Logical Replication Docs |