Re: remove some STATUS_* symbols - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: remove some STATUS_* symbols
Date
Msg-id 4edc8a92-373c-1a4d-eded-6b342f0890dc@2ndquadrant.com
Whole thread Raw
In response to Re: remove some STATUS_* symbols  (Michael Paquier <michael@paquier.xyz>)
Responses Re: remove some STATUS_* symbols  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: ALTER TABLE support for dropping generation expression
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup fails on databases with high OIDs