Re: BUG #19686: Rolling back SET TABLESPACE

From: Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19686: Rolling back SET TABLESPACE
Date: 2026-09-30 07:23:25
Message-ID: CAE8JnxPp+FN38=qTSFdnh67-u7wE6NqG2-Cc-ECUwO+BUG0XrQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you all.

Was good to see so many reviews in such a short time.

Given that the expected behaviour is to copy only the heap.
Indexes get corrupted on modifications.
We shouldn't push the cost to commit.

What if we simply block modifications to the table in a transaction
after it moved to a new tablespace?

Regards,
Alexandre

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Xuneng Zhou 2026-09-30 07:32:03 Re: test: avoid redundant standby catchup in 049_wait_for_lsn
Previous Message Trakshan Mishra 2026-09-30 07:22:18 Re: Re: [PATCH] Clear FatalError earlier during crash restart