| From: | Maxim Orlov <orlovmg(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: POC: make mxidoff 64 bits |
| Date: | 2025-10-30 06:13:54 |
| Message-ID: | CACG=ezaABYDepYf24MUNxc2oHRERxXbXHNMP+i-Pr1AXu26x0A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Unfortunately, I need to admit that I have messed a bit with v18.
I forgot to sync the pg_upgrade portion with the rest of the patch,
among other things. Here's a proper version with additional testing.
pg_upgrade/t/007_mxoff.pl is not meant to be committed, it's just
for test purposes. In order to run it, env var oldinstall must be set.
On Tue, 28 Oct 2025 at 17:17, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> On 27/10/2025 17:54, Maxim Orlov wrote:
>
>
> If backend C looks up multixid 101 in between steps 3 and 4, it would
> read the offset incorrectly, because 'base' isn't set yet.
>
> Hmm, maybe I miss something? We set page base on first write of any
offset on the page, not only the first one. In other words, there
should never be a case when we read an offset without a previously
defined page base. Correct me if I'm wrong:
1. Backend A assigned mxact=100, offset=1000.
2. Backend B assigned mxact=101, offset=1010.
3. Backend B calls RecordNewMultiXact()/MXOffsetWrite() and
set page base=1010, offset plus 0^0x80000000 bit while
holding lock on the page.
4. Backend C looks up for the mxact=101 by calling MXOffsetRead()
and should get exactly what he's looking for:
base (1010) + offset (0) minus 0x80000000 bit.
5. Backend A calls RecordNewMultiXact() and sets his offset using
existing base from step 3.
--
Best regards,
Maxim Orlov.
| Attachment | Content-Type | Size |
|---|---|---|
| v19-0005-Add-test-for-64-bit-mxoff-in-pg_upgrade.patch.txt | text/plain | 11.5 KB |
| v19-0003-Add-test-for-64-bit-mxoff-in-pg_resetwal.patch | application/octet-stream | 4.9 KB |
| v19-0001-Use-64-bit-multixact-offsets.patch | application/octet-stream | 32.0 KB |
| v19-0004-TEST-bump-catversion.patch.txt | text/plain | 773 bytes |
| v19-0002-Add-pg_upgarde-for-64-bit-multixact-offsets.patch | application/octet-stream | 34.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wenhui qiu | 2025-10-30 06:48:18 | Re: another autovacuum scheduling thread |
| Previous Message | Peter Smith | 2025-10-30 06:04:05 | Re: Skipping schema changes in publication |