"Steve Woodcock" <steve.woodcock@gmail.com> writes:
> On 01/05/06, Scott Sipe <cscotts@mindspring.com> wrote:
>> So, my question is, before I do any further digging, is super-smack
>> flawed?
> Hmm, selects and updates of a 90k row table using the primary key, but
> no sign of a VACUUM ANALYZE...
Reasonably recent versions of PG should be able to do "the right thing"
in the presence of a simple primary key, even without any prior ANALYZE;
the planner will see the unique index and make the right conclusions
about statistics.
If the test is doing a huge number of UPDATEs and no VACUUM anywhere,
then accumulation of dead rows would eventually hurt, but it's not clear
from Scott's report if that's the issue.
I'm inclined to think there's some more subtle bias in the testbed.
I haven't dug into the code to look at how they are managing multiple
connections, but I wonder if say there's something causing the client to
not notice responses from the server right away when it's going through
libpq.
FWIW, my own experiments with tests like this suggest that PG is at
worst about 2x slower than mysql for trivial queries. If you'd reported
a result in that ballpark I'd have accepted it as probably real. 6x I
don't believe though ...
regards, tom lane
