Horton

Re: API stability

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

View thread View on postgr.es
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: robertmhaas@gmail.com
Cc: markus.wanner@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2022-04-06T06:31:53Z
Lists: pgsql-hackers 
At Wed, 06 Apr 2022 14:30:37 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> So if we don't want to move any member in PGPROC, we do:
> 
> 14: after statusFlags.
> 13: after delayChkpt.
> 12-10: after syncRepState (and before syncRepLinks).
> 
> If we allow to shift some members, the new flag can be placed more
> saner place.
> 
> 14: after delayChkpt ((uint8)statusFlags moves forward by 1 byte)
> 13: after delayChkpt (no member moves)
> 12-10: after subxids ((bool)procArrayGroupMember moves forward by 1 byte)
> 
> I continue working on the last direction above.

Hmm. That is ABI break.  I go with the first way.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Commits

  1. Rethink the delay-checkpoint-end mechanism in the back-branches.

  2. Rename delayChkpt to delayChkptFlags.

  3. Fix possible recovery trouble if TRUNCATE overlaps a checkpoint.