Re: [HACKERS] [PATCH] Use correct types and limits for PL/Perl SPI query results

ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes: > Tom Lane writes: >> I thought about using UV where feasible, but it was not clear to me >> whether unsigned numbers behave semantically differently from signed ones >> in Perl. If they do, the change you

Re: [HACKERS] [PATCH] Use correct types and limits for PL/Perl SPI query results

Tom Lane writes: > ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes: >> 1) Perl's integers are at least pointer-sized and either signed or >>unsigned, so can potentially hold up to 2⁶⁴-1. Floating point numbers >>can also be larger than double (up

Re: [HACKERS] [PATCH] Use correct types and limits for PL/Perl SPI query results

ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes: > 1) Perl's integers are at least pointer-sized and either signed or >unsigned, so can potentially hold up to 2⁶⁴-1. Floating point numbers >can also be larger than double (up to 128bit), allowing for exact >

[HACKERS] [PATCH] Use correct types and limits for PL/Perl SPI query results

Hi hackers, Commit 23a27b039d94ba359286694831eafe03cd970eef changed the type of numbers-of-tuples-processed counters to uint64 and adjusted various PLs to cope with this. I noticed the PL/Perl changes did not take full advantage of what Perl is capable of handling, so here's a patch that