>
> Michael, you nailed it again. My libpq test C program delivered
> between 2400 QPS and 5000 QPS vs ~10 QPS for DBI/DBD::Pg on this
> box.
>
> It remains unclear to me why the same DBI/DBD::Pg client code
> would deliver performance 2-3 orders of magnitude better on
> other roughly comparable or inferior boxes.
>
I'm using DBD::Pg for some large inserts(well, they were large) most of it
was pretty reasonable, there were some quirky things, like last_insert_id
is/was incredibly slow(it's very smart, but the way it does things makes the
performance horrible) doing the currval call yourself is much faster.
I found that using the Perl profiler identified a couple things like that
and let me get things to a reasonable speed.
-Steve
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
