| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | robertmhaas(at)gmail(dot)com |
| Cc: | markus(dot)wanner(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: API stability |
| Date: | 2022-04-06 06:31:53 |
| Message-ID: | 20220406.153153.746094489184530420.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
At Wed, 06 Apr 2022 14:30:37 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2022-04-06 06:52:37 | pgsql: Allow asynchronous execution in more cases. |
| Previous Message | Peter Eisentraut | 2022-04-06 06:18:55 | pgsql: Update Unicode data to CLDR 41 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-04-06 06:53:32 | Re: API stability |
| Previous Message | Amit Kapila | 2022-04-06 05:58:29 | Re: Logical replication timeout problem |