Richard Jones wrote:

>A good first step for PostgreSQL is to use and understand the "VACUUM"
>and "EXPLAIN" commands, and to turn on statement logging (with
>timestamps) so you can see which queries are consuming the most time.
>
>  
>
I'd add the "COPY" command to that list, with the attendent understand 
of why INSERTs are slow on Postgresql.  But this is off-topic for this list.

Brian