Re: ALTER INDEX .. RENAME allows to rename tables/views as well - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: ALTER INDEX .. RENAME allows to rename tables/views as well
Date
Msg-id 0D4F5321-E95A-4806-A193-AD50D3F8E367@amazon.com
Whole thread Raw
In response to Re: ALTER INDEX .. RENAME allows to rename tables/views as well  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On 10/19/21, 3:13 PM, "Alvaro Herrera" <alvherre@alvh.no-ip.org> wrote:
> On 2021-Oct-19, Bossart, Nathan wrote:
>
>> I did consider this, but I figured it might be better to keep the lock
>> level consistent for a given object type no matter what the statement
>> type is.  I don't have a strong opinion about this, though.
>
> Yeah, the problem is that if there is a concurrent process waiting on
> your lock, we'll release ours and they'll grab theirs, so we'll be
> waiting on them afterwards, which is worse.

Makes sense.

> BTW I noticed that the case of partitioned indexes was wrong too.  I
> fixed that, added it to the tests, and pushed.

Ah, good catch.  Thanks!

Nathan


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
Next
From: Mark Dilger
Date:
Subject: Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)