Re: Use MaxLockMode in lock methods initialization

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Use MaxLockMode in lock methods initialization
Date: 2022-01-03 08:00:13
Message-ID: YdKtDbxrgjjBUs+e@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-01-03 08:17:20 Re: Remove inconsistent quotes from date_part error
Previous Message Michael Paquier 2022-01-03 07:56:39 Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory