Re: POC: make mxidoff 64 bits

zengman <zengman@halodbtech.com>

From: zengman <zengman@halodbtech.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-05T03:56:46Z
Lists: pgsql-hackers
> > I'm currently looking into the `SlruReadSwitchPageSlow` function and have a question regarding the expression `&state->buf.data + bytes_read` โ€”
> > I suspect the ampersand (&) here might be misused. Would you be able to help me verify this?

> Yes, you're right. Good catch! Committed the fix, thanks.

Thank you for confirming this, committing the fix, and recognizing this.๐Ÿ˜€

--
Regards,
Man Zeng
www.openhalo.org

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference โ†’
  1. Fix partial read handling in pg_upgrade's multixact conversion

  2. Increase timeout in multixid_conversion upgrade test

  3. Improve sanity checks on multixid members length

  4. Clarify comment on multixid offset wraparound check

  5. Never store 0 as the nextMXact

  6. Add runtime checks for bogus multixact offsets

  7. Widen MultiXactOffset to 64 bits

  8. Move pg_multixact SLRU page format definitions to a separate header

  9. Convert confusing macros in multixact.c to static inline functions

  10. Index SLRUs by 64-bit integers rather than by 32-bit integers

  11. Cope with possible failure of the oldest MultiXact to exist.