Re: Making type Datum be 8 bytes everywhere

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Making type Datum be 8 bytes everywhere
Date: 2025-07-30 15:48:08
Message-ID: 1517712.1753890488@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> writes:
> On Wed, 23 Jul 2025 at 22:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm disinclined to put in a huge amount of effort looking for the
>> worst case. We established long ago that we weren't going to
>> optimize for 32-bit anymore. So as long as this doesn't completely
>> tank performance on 32-bit, I'm satisfied. I'd almost say that
>> if standard pgbench doesn't notice the change, that's good enough.

> I did a basic pgbench benchmark on a 32-bit build and there is no change.

Thanks for doing that! For me, that's enough evidence to move
forward.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-07-30 15:51:58 Assertion failure in pgbench
Previous Message Xuneng Zhou 2025-07-30 15:42:10 Re: Add progressive backoff to XactLockTableWait functions