| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Maxim Orlov <orlovmg(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: POC: make mxidoff 64 bits |
| Date: | 2025-12-10 19:19:18 |
| Message-ID: | b3e13089-fa03-4241-b203-1ba140ef86dc@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/12/2025 14:00, Heikki Linnakangas wrote:
> 1. Currently, at multixid wraparound, MultiXactState->nextMXact goes to
> 0, which is invalid. All the readers must be prepared for that, and skip
> over the 0. That's error-prone, we've already missed that a few times.
> Let's change things so that the code that *writes* MultiXactState-
> >nextMXact skips over the zero already.
Here's a patch for that. Does anyone see a problem with this?
- Heikki
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-refactor-Never-store-0-as-the-nextMXact.patch | text/x-patch | 10.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-12-10 19:32:37 | Re: Solaris versus our NLS files |
| Previous Message | Tom Lane | 2025-12-10 18:52:41 | Re: Solaris versus our NLS files |