Re: Speedup usages of pg_*toa() functions
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
Andres Freund <andres@anarazel.de>
Date: 2020-06-13T00:36:36Z
Lists: pgsql-hackers
On Thu, 11 Jun 2020 at 18:52, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote: > > >>>>> "David" == David Rowley <dgrowleyml@gmail.com> writes: > > David> Pending any objections, I'd like to push both of these patches > David> in the next few days to master. > > For the second patch, can we take the opportunity to remove the > extraneous blank line at the top of pg_ltoa, and add the two missing > "extern"s in builtins.h for pg_ultoa_n and pg_ulltoa_n ? > > David> Anyone object to changing the signature of these functions in > David> 0002, or have concerns about allocating the maximum memory that > David> we might require in int8out()? > > Changing the function signatures seems safe enough. The memory thing > only seems likely to be an issue if you allocate a lot of text strings > for bigint values without a context reset, and I'm not sure where that > would happen (maybe passing large bigint arrays to pl/perl or pl/python > would do it?) I ended up chickening out of doing the larger allocation unconditionally. Instead, I pushed the original idea of doing the palloc/memcpy of the length returned by pg_lltoa. That gets us most of the gains without the change in memory usage behaviour. Thanks for your reviews on this. David
Commits
-
Have pg_itoa, pg_ltoa and pg_lltoa return the length of the string
- dad75eb4a8d5 14.0 landed
-
Add missing extern keyword for a couple of numutils functions
- 095f2d95c927 13.0 landed
- 9a7fccd9eac8 14.0 landed