Re: remove some STATUS_* symbols

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remove some STATUS_* symbols
Date: 2020-01-11 07:14:17
Message-ID: 4edc8a92-373c-1a4d-eded-6b342f0890dc@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-01-10 06:23, Michael Paquier wrote:
> On Thu, Jan 09, 2020 at 11:15:08AM +0100, Peter Eisentraut wrote:
>> You mean put he subsequent GrantLock() calls into LockCheckConflicts()? That
>> would technically save some duplicate code, but it seems weird, because
>> LockCheckConflicts() is notionally a read-only function that shouldn't
>> change state.
>
> Nah. I was thinking about the first part of this "if" clause
> LockCheckConflicts is part of here:
> if (lockMethodTable->conflictTab[lockmode] & lock->waitMask)
> status = STATUS_FOUND;
> else
> status = LockCheckConflicts(lockMethodTable, lockmode,
> lock, proclock);
>
> But now that I look at it closely it messes up heavily with
> ProcSleep() ;)

OK, pushed as it was then.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-01-11 07:21:11 Re: pg_basebackup fails on databases with high OIDs
Previous Message Peter Eisentraut 2020-01-11 06:35:44 Re: ALTER TABLE support for dropping generation expression