On 23 Jul 2003 at 16:05, Jean-Christian Imbeault wrote:
> I have a database which is constantly being written to. A web server's
> log file (and extras) is being written to it. There are no deletions or
> updates (at least I think so :).
> As the web traffic increases so will the write intensity.
> Right now the database tables have no foreign keys defined even though
> there are foreign keys. The code that inserts into the DB is simple
> enough (now) that we can make sure that nothing is inserted if the
> corresponding fk does not exist and that all fk checks pass.
> I want to add foreign key constraints to the table definitions but I am
> worried that it might be a big performance hit. Can anyone tell me how
> much of a performance hit adding one foreign key constraint to one field
> in a table will roughly be?
> Also, for a DB that is write-intensive and rarely read, what are some
> things I can do to increase performance? (Keeping in mind that there is
> more than on DB on the same pg server).
1. Insert them in batches. Proper size of transactions can speed the write
2. What kind of foreign keys you have? It might be possible to reduce FK
overhead if you are checking against small number of records.
3. Tune your hardware for write performance like getting a good-for-write RAID.
I forgot which performs which for read and write.
4. Tune WAL and move it to separate drive. That should win you some
Beauty: What's in your eye when you have a bee in your hand.