> * set reasonable statement timeout
> * backup with pitr. pg_dump is a headache on extremely busy servers.
Where do you put your pitr wal logs so that they don't take up extra
I/O ?
> * get good i/o system for your box. start with 6 disk raid 10 and go
> from there.
> * spend some time reading about bgwriter settings, commit_delay, etc.
> * keep an eye out for postgresql hot (hopefully coming with 8.3) and
> make allowances for it in your design if possible.
> * normalize your database and think of vacuum as dangerous enemy.
>
> good luck! :-)
>
> merlin
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
