> Foreign keys have zero, nada, zilch to do with the performance of
> count(*).
OK, I just wanted to make sure.
> The only plausible theory I can think of for the performance
> difference is that in your "new" database the table has been through
> several mass updates, leading to a whole lot of dead rows and a much
> larger physical table size to scan through. I'd suggest a VACUUM
> VERBOSE on both old and new copies of the table to get an idea of the
> relative physical sizes. You might need a VACUUM FULL to get the new
> table back down to a reasonable size...
Oh good lord.
*waves the Idiot Flag as he slinks back under his rock*
Thank you, Tom, for your patience. That was it. I'm a potatohead,
but I'm learning. :)
Benny, swearing he DID do a vacuum, but obviously not...
--
"Even if a man chops off your hand with a sword, you still have two nice,
sharp bones to stick in his eyes."
-- .sig on Slashdot
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
