Re: Define DatumGetInt8 function.

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Define DatumGetInt8 function.
Date: 2026-01-06 14:21:55
Message-ID: CAJ7c6TPsaLW7O67vqv8YyV_qUUjF0pncDB7dCQJFDw0so7wrdw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> > Kirill, are you working on this patch?
>
> Yes, PFA.
>
> > I've not studied in detail,
> > but looks like it would require making
> > char_decrement()/char_increment() and btcharskipsupport() all use
> > CharGetDatum()/DatumGetChar() and switch to using SCHAR_MIN/SCHAR_MAX
> > rather than 0/UCHAR_MAX.
>
> This is also a possible change, and can be a separate patch. I will
> try to also work on this this week.

v1 looks incomplete to me. As I understand, Tom proposed to get rid of
UInt8 conversions as well. Are you going to implement this idea as
well?

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-01-06 14:23:43 Re: Refactor PROCLOCK hash table into partitioned list allocator
Previous Message Corey Huinker 2026-01-06 14:12:50 Re: Import Statistics in postgres_fdw before resorting to sampling.