pg: Adventures in writing a new postgresql client
This commit is contained in:
parent
0d19ccdc1b
commit
b242176071
7 changed files with 132 additions and 4 deletions
|
|
@ -17,6 +17,9 @@ be a good measure". I've used these benchmarks to find and optimize hotspots in
|
|||
FU, which in turn means these numbers may look better than they are in
|
||||
real-world use.
|
||||
|
||||
B<DISCLAIMER#3:> Many of these benchmarks exists solely to test edge case
|
||||
performance, these numbers are not representative for real-world use.
|
||||
|
||||
=head1 MODULE VERSIONS
|
||||
|
||||
The following module versions were used:
|
||||
|
|
@ -39,7 +42,7 @@ The following module versions were used:
|
|||
|
||||
=head1 BENCHMARKS
|
||||
|
||||
=head2 JSON Formatting
|
||||
=head2 JSON Parsing & Formatting
|
||||
|
||||
These benchmarks run on large-ish arrays with repeated values. JSON encoding is
|
||||
sufficiently fast that Perl function calling overhead tends to dominate for
|
||||
|
|
|
|||
11
FU/PG.pm
Normal file
11
FU/PG.pm
Normal file
|
|
@ -0,0 +1,11 @@
|
|||
package FU::PG 0.1;
|
||||
use v5.36;
|
||||
use FU::XS;
|
||||
|
||||
_load_libpq();
|
||||
|
||||
package FU::PG::conn {
|
||||
sub lib_version { FU::PG::lib_version() }
|
||||
};
|
||||
|
||||
1;
|
||||
Loading…
Add table
Add a link
Reference in a new issue