Re: ALTER INDEX .. RENAME allows to rename tables/views as well

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Onder Kalaci <onderk(at)microsoft(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER INDEX .. RENAME allows to rename tables/views as well
Date: 2021-10-19 20:36:04
Message-ID: 202110192036.ierdjj5axhk3@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I was about to push this when it occurred to me that it seems a bit
pointless to release AEL in order to retry with the lighter lock; once
we have AEL, let's just keep it and proceed. So how about the attached?

I'm now thinking that this is to back-patch all the way to 12.

--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/

Attachment Content-Type Size
v3-0001-Ensure-correct-lock-level-is-used-in-ALTER-.-RENA.patch text/x-diff 7.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-10-19 20:43:59 Re: ThisTimeLineID can be used uninitialized
Previous Message Bossart, Nathan 2021-10-19 20:20:44 Re: pg_upgrade test chatter