>You are mistaken to think that CPU is the bottleneck, anyway. It is
>going to be disk bandwidth that's your problem, and throwing more CPUs
>at it would not help. If your insert load exceeds the available disk
>bandwidth, I think you have little choice but to figure out a way to
>divide the workload among multiple independent databases.
>
>
>
If you have the money to purchase multiple machines, you can throw more
hard drives at it...
Hard drives are cheap... (well ide/sata anyway).
Sincerely,
Joshua D. Drake
> regards, tom lane
>
>---------------------------(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
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
