Re: Why postgres take RowExclusiveLock on all partition - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why postgres take RowExclusiveLock on all partition
Date
Msg-id 18090.1474035072@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why postgres take RowExclusiveLock on all partition  (Sachin Kotwal <kotsachin@gmail.com>)
Responses Re: Why postgres take RowExclusiveLock on all partition  (Sachin Kotwal <kotsachin@gmail.com>)
List pgsql-hackers
Sachin Kotwal <kotsachin@gmail.com> writes:
> Does it release locks after taking decision and then perform actual update
> operation on partition table?

No, there's no attempt to do that, and we're unlikely to consider doing so
because it would result in more lock-table thrashing.  Why do you care?
RowExclusiveLock does not block any normal DML operation, so there's no
apparent benefit from releasing it early.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: OpenSSL 1.1 breaks configure and more
Next
From: Robert Haas
Date:
Subject: Re: [PROPOSAL][PROTOTYPE] Individual options for each index column: Opclass options