Re: Use MaxLockMode in lock methods initialization
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Julien Rouhaud <rjuju123@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2022-01-03T17:27:18Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > On Mon, Jan 03, 2022 at 02:47:22PM +0800, Julien Rouhaud wrote: >> While reading some code around I noticed that b04aeb0a053e7 added a MaxLockMode >> but didn't update the lock methods initialization. It shouldn't make much >> difference in the long run but some consistency seems better to me. > Makes sense to me. MaxLockMode is here for the same purpose as this > initialization area. Agreed. That aspect of b04aeb0a053e7 was a bit of a quick hack, and it didn't occur to me to look for other places where the symbol could be used. But these two places are spot-on for it. Pushed with a bit of comment-fiddling. regards, tom lane
Commits
-
Use MaxLockMode symbol in more places.
- ba2bc4a7bace 15.0 landed