Re: POC: make mxidoff 64 bits

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: 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: 2024-10-23 15:55:06
Message-ID: CACG=ezYFNqGjsxF6Vb2CHF6JzKcjhAFauaFm9js0nu_3Ngcdkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

After a bit of thought, I've realized that to be conservative here is the
way to go.

We can reuse a maximum of existing logic. I mean, we can remove offset
wraparound "error logic" and reuse "warning logic". But set the threshold
for "warning logic" to a much higher value. For now, I choose 2^32-1. In
other world, legit logic, in my view, here would be to trigger autovacuum
if the number of offsets (i.e. difference nextOffset - oldestOffset)
exceeds 2^32-1. PFA patch set.

--
Best regards,
Maxim Orlov.

Attachment Content-Type Size
v5-0002-Use-64-bit-multixact-offsets.patch application/octet-stream 13.3 KB
v5-0003-Make-pg_upgrade-convert-multixact-offsets.patch application/octet-stream 12.4 KB
v5-0004-Get-rid-of-MultiXactMemberFreezeThreshold-call.patch application/octet-stream 8.8 KB
v5-0001-Use-64-bit-format-output-for-multixact-offsets.patch application/octet-stream 9.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-10-23 16:04:30 Re: Using Expanded Objects other than Arrays from plpgsql
Previous Message Daniel Gustafsson 2024-10-23 15:46:14 Re: [PoC] Federated Authn/z with OAUTHBEARER