Re: Improving and extending int128.h to more of numeric.c - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: Improving and extending int128.h to more of numeric.c
Date
Msg-id CAEZATCWjPZ6w_JZDZmDJPJhYKKJZx8ywxbZYbvSbtrtKyvN-qw@mail.gmail.com
Whole thread Raw
In response to Re: Improving and extending int128.h to more of numeric.c  (John Naylor <johncnaylorls@gmail.com>)
List pgsql-hackers
On Fri, 18 Jul 2025 at 07:42, John Naylor <johncnaylorls@gmail.com> wrote:
>
> While testing something else on s390x, I noticed that __int128 support
> is broken on that platform at least for some versions of clang [1],
> and I see improvement there with this patch:
>
> Query 1:
> HEAD:  3015ms
> Patch: 2206ms
>
> Query 2:
> HEAD:  3394ms
> Patch: 2514ms

Thanks for testing.

On Fri, 18 Jul 2025 at 07:47, John Naylor <johncnaylorls@gmail.com> wrote:
>
> On Thu, Jul 17, 2025 at 2:30 PM Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> >
> > BTW, my other motivation for doing this was to simplify the numeric
> > code. Even if this had zero performance benefit, as long as it didn't
> > make things any slower, I would argue that it's worth doing.
>
> I gathered that was the main motivation, and I agree. I looked over
> 0005 and don't see any issues.

Thanks for reviewing. If there are no objections, I'll push this
shortly (though I'll change INT64_HEX_FORMAT to PRIx64, since it looks
like the former is about to go away).

Regards,
Dean



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events
Next
From: Fujii Masao
Date:
Subject: Re: Bug in pg_dump --filter? - Invalid object types can be misinterpreted as valid