Re: PGPROC alignment (was Re: pgsql: Separate RecoveryConflictReasons from procsignals) - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: PGPROC alignment (was Re: pgsql: Separate RecoveryConflictReasons from procsignals)
Date
Msg-id f7bd155e-0bd4-4b09-86b3-92140af98654@iki.fi
Whole thread Raw
In response to Re: PGPROC alignment (was Re: pgsql: Separate RecoveryConflictReasons from procsignals)  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers
On 11/02/2026 06:40, Bertrand Drouvot wrote:
> On Tue, Feb 10, 2026 at 10:53:58PM +0200, Heikki Linnakangas wrote:
> 0003:
> 
> 1/ There is one missing change in PrintLockQueue() ("links" is still used, and
> that should be replaced by "waitLink").
> 
> 2/ change the comment on top of ProcWakeup?
> 
> "
> /*
>   * ProcWakeup -- wake up a process by setting its latch.
>   *
>   *   Also remove the process from the wait queue and set its links invalid.
> "
> 
> s/links/waitLink/?

Fixed those and pushed this "Split PGPROC 'links' field into two, for 
clarity" patch. Thanks for the review!

- Heikki




pgsql-hackers by date:

Previous
From: Harinath Kanchu
Date:
Subject: Re: Streaming replication and WAL archive interactions
Next
From: Heikki Linnakangas
Date:
Subject: Re: PGPROC alignment (was Re: pgsql: Separate RecoveryConflictReasons from procsignals)