Re: Using 128-bit integers for sum, avg and statistics aggregates - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Using 128-bit integers for sum, avg and statistics aggregates
Date
Msg-id 550A06E6.1030906@proxel.se
Whole thread Raw
In response to Re: Using 128-bit integers for sum, avg and statistics aggregates  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Using 128-bit integers for sum, avg and statistics aggregates  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 03/18/2015 11:59 PM, Peter Geoghegan wrote:
> Okay. Attached revision has a few tweaks that reflect the status of
> int128/uint128 as specialized types that are basically only useful for
> this optimization, or other similar optimizations on compilers that
> either are GCC, or aim to be compatible with it. I don't think
> Andreas' V9 reflected that sufficiently.
>
> Also, I now always use PolyNumAggState (the typedef), even for #define
> HAVE_INT128 code, which I think is a bit clearer. Note that I have
> generated a minimal diff, without the machine generated changes that
> are ordinarily included in the final commit when autoconf tests are
> added, mostly because I do not have the exact version of autoconf on
> my development machine required to do this without creating irrelevant

Thanks,

I have attached a patch where I have ran autoconf.

--
Andreas Karlsson

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: parallel mode and parallel contexts
Next
From: Michael Paquier
Date:
Subject: Re: Strange assertion using VACOPT_FREEZE in vacuum.c