Re: BUG #19686: Rolling back SET TABLESPACE

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>
Cc: Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19686: Rolling back SET TABLESPACE
Date: 2026-10-18 04:39:40
Message-ID: CAGRkXqRKCNG1LKBV7d98QSdZKf1iT8Qb7LM9jTDKofn33hdsyw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Manu,

One correction. v7 copies the indexes in their own tablespace, so the
room is needed on the old volume, not the destination.

That means a driver sending a single ALTER fails when the old volume
is nearly full, while master works:

master: ALTER TABLE
v7: ERROR: could not extend file "pg_tblspc/...": No space
left on device

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-18 04:41:00 Re: [PG19] Bugs found comparing 19 with 18, list before I open threads
Previous Message shihao zhong 2026-10-18 04:39:13 [PG19] A canceled notify read leaves the NOTIFY queue stuck