| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Slim down integer formatting |
| Date: | 2021-07-27 02:42:42 |
| Message-ID: | YP9yolkVjYSCvxUF@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 27, 2021 at 12:28:22PM +1000, Greg Nancarrow wrote:
> That patch didn't apply for me (on latest source) so I've attached an
> equivalent with those changes, that does apply, and also tweaks the
> Makefile include path to address that #include issue.
When applying some micro-benchmarking to stress those APIs, how much
does this change things? At the end of the day, this also comes down
to an evaluation of pg_ulltoa_n() and pg_ultoa_n().
#include "common/int.h"
+#include "d2s_intrinsics.h"
Er, are you sure about this part? The first version of the patch did
that in a different, also incorrect, way.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2021-07-27 02:53:14 | Re: Slim down integer formatting |
| Previous Message | Bruce Momjian | 2021-07-27 02:39:17 | Re: visibility map corruption |