A furthur thought or two:
- you are *sure* that it is Postgres that is slow? (could be Php...or your
machine could be out of some resource - see next 2 points)
- is your machine running out of cpu or memory?
- is your machine seeing huge io transfers or long io waits?
- are you running Php on this machine as well as Postgres?
- what os (and what release) are you running? (guessing Linux but...)
As an aside, they always say this but: Postgres 7.4 generally performs better
than 7.3...so an upgrade could be worth it - *after* you have solved/identified
the other issues.
Quoting Stephane Tessier <[EMAIL PROTECTED]>:
> Hi everyone,
> somebody can help me??????? my boss want to migrate to
> we have a BIG problem of performance,it's slow....
> we use postgres 7.3 for php security application with approximately 4
> millions of insertion by day and 4 millions of delete and update
> and archive db with 40 millions of archived stuff...
> we have 10 databases for our clients and a centralized database for the
> general stuff.
> database specs:
> double XEON 2.4 on DELL PowerEdge2650
> 2 gigs of RAM
> 5 SCSI Drive RAID 5 15rpm
> 4 millions of transactions by day
> 160 open connection 24 hours by day 7 days by week
> pg_autovacuum running 24/7
> reindex on midnight
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match