Postgres Pro
Downloads
Home   >   mailing lists

Re: Locking for Rename To new_name works differently for different objects - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Locking for Rename To new_name works differently for different objects
Date
Msg-id 4539.1413381892@sss.pgh.pa.us
Whole thread Raw
In response to Locking for Rename To new_name works differently for different objects  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Locking for Rename To new_name works differently for different objects
List pgsql-hackers
Tree view 
Amit Kapila <amit.kapila16@gmail.com> writes:
> I have observed that for renaming some of the objects
> AccessExclusiveLock is taken on object whereas for
> other kind of objects no lock is taken on object before
> renaming the object.

The usual theory for DDL updates of all types (not just rename)
is that an explicit lock is only needed for objects whose catalog
representation comprises more than one row.  Otherwise, the implicit
locking involved in updating that row is sufficient to serialize
different updates.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Kouhei Kaigai
Date:
Subject: Re: How to make ResourceOwnerForgetBuffer() O(1), instead of O(N^2) scale
Next
From: Simon Riggs
Date:
Subject: Re: group locking: incomplete patch, just for discussion