Re: Speed up transaction completion faster after many relations are accessed in a transaction - Mailing list pgsql-hackers

From Ankit Kumar Pandey
Subject Re: Speed up transaction completion faster after many relations are accessed in a transaction
Date
Msg-id 166749012522.1122.11683450499316408651.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Speed up transaction completion faster after many relations are accessed in a transaction  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Speed up transaction completion faster after many relations are accessed in a transaction
List pgsql-hackers
Hi David,

This is review of speed up releasing of locks patch.

Contents & Purpose:
Subject is missing in patch. It would have been easier to understand purpose had it been included.
Included in the patch are change in README, but no new tests are included..

Initial Run:
The patch applies cleanly to HEAD. The regression tests all pass
successfully against the new patch.

Nitpicking & conclusion:
I don't see any performance improvement in tests. Lots of comments
were removed which were not fully replaced. Change of log level for ReleaseLockIfHeld: failed
from warning to panic is mystery. 
Change in readme doesn't look right.
`Any subsequent lockers are share lockers wait 
waiting for the VXID to terminate via some other method) is for deadlock`. This sentence could be rewritten.
Also more comments could be added to explain new methods added.

Thanks,
Ankit

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUG] Logical replica crash if there was an error in a function.
Next
From: Alvaro Herrera
Date:
Subject: Re: parse partition strategy string in gram.y