Hi Mischa,
You probably need to determine whether the bottleneck is cpu or disk (should be
easy enough!)
Having said that, assuming your application is insert/update intensive I would
recommend:
- mount the ufs filesystems Pg uses *without* logging
- use postgresql.conf setting fsync_method=fdat
Stephen,
> " -> Seq Scan on island_history (cost=0.00..417867.13 rows=292274
> width=83) (actual time=346759.000..346759.000 rows=10 loops=1)"
Take a look at your row comparisons. When was the last time you ran ANALYZE?
--
Josh Berkus
Aglio Database Solutions
San Francisco
---