Re: POC: make mxidoff 64 bits

From: Maxim Orlov <orlovmg(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, 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: 2026-02-21 14:59:21
Message-ID: CACG=ezbccQucKvp9a-3zKmoCFjsXo1RNkYVJ9i7ZBhJH+4hJDg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 20 Feb 2026 at 11:47, Maxim Orlov <orlovmg(at)gmail(dot)com> wrote:

>
> Just one more minor thing. While working on making CLOG 64-bit, I
>
After a short break, I realized this patch still doesn't do it correctly.
For transactions that have a real epoch, it won't display it; in fact, it
will
show a zero epoch.

Apparently, we need to output the epoch only when it is different from 0.
If it is equal to 0, then output with just %u

--
Best regards,
Maxim Orlov.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2026-02-21 15:01:08 Partial Mode in Aggregate Functions
Previous Message jian he 2026-02-21 14:42:59 Re: alter check constraint enforceability