Re: pgsql: Separate RecoveryConflictReasons from procsignals - Mailing list pgsql-committers

From Bertrand Drouvot
Subject Re: pgsql: Separate RecoveryConflictReasons from procsignals
Date
Msg-id aYtMbb28qxqLrhvC@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to pgsql: Separate RecoveryConflictReasons from procsignals  (Heikki Linnakangas <heikki.linnakangas@iki.fi>)
Responses Re: pgsql: Separate RecoveryConflictReasons from procsignals
List pgsql-committers
Hi,

On Tue, Feb 10, 2026 at 02:32:37PM +0000, Heikki Linnakangas wrote:
> Separate RecoveryConflictReasons from procsignals
> 
> Share the same PROCSIG_RECOVERY_CONFLICT flag for all recovery
> conflict reasons. To distinguish, have a bitmask in PGPROC to indicate
> the reason(s).

I did not look at the thread, so sorry to be late, but that makes the size of PGPROC
going from 832 to 840 bytes, so not a multiple of 64 anymore. Is that something
to worry about? (same kind of discussion in [1]).

[1]: https://postgr.es/m/tw53roer2j4quxh7vlyv62drc5fo6c6zdltvl6d2dttqa62uhi%40stwlpdwlftpj

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Refactor ProcessRecoveryConflictInterrupt for readability
Next
From: Heikki Linnakangas
Date:
Subject: Re: pgsql: Separate RecoveryConflictReasons from procsignals