Re: BUG #19686: Rolling back SET TABLESPACE

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19686: Rolling back SET TABLESPACE
Date: 2026-10-04 19:14:42
Message-ID: CAGRkXqSwuvuYrKdf5o9Jn=JqkdO7YT0+nTS6L9tf_+Hu-_gWaQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Manu,

I think v7 is correct, but I am not sure it is better than v6.

v6 keeps the shortcut for both protocols. Its cost is that a
pipelined ALTER commits on its own, but I think few people send
SET TABLESPACE in a pipeline with other statements.

v7 changes no behavior, but the shortcut only helps simple protocol
clients. For me that means mostly psql.

I personally prefer v6, but that should be a committer decision.

Thanks,
Shihao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-04 20:04:18 Re: BUG #19686: Rolling back SET TABLESPACE
Previous Message Joe Conway 2026-10-04 19:04:49 Re: Request to expedite cool-off