| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Greg Nancarrow <gregn4422(at)gmail(dot)com>, 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:53:14 |
| Message-ID: | CAApHDvpNmxZKksaGEQ4g2KKtpro5uNhhx4ywT4e+H5rG21OHKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 27 Jul 2021 at 14:42, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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().
I'd suggest something like creating a table with, say 1 million INTs
and testing the performance of copy <table> to '/dev/null';
Repeat for BIGINT
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Nancarrow | 2021-07-27 03:08:26 | Re: Slim down integer formatting |
| Previous Message | Michael Paquier | 2021-07-27 02:42:42 | Re: Slim down integer formatting |