Postgres optimization for insert / read

I am working on a database with the following characteristics:

  • Many inserts (in the range of 1 fps)
  • Many data indices, complex joins
  • NO Deletes or updates, only inserts, reads, and table drops
  • I don't care if reading into the database reflects the exact state.
  • Data is not critical, I already run fsync = off

I already know a little about postgres optimization, but I was hoping there might be some additional tricks that are more suitable for my particular use case.

+3
source share
2 answers

, ( 9.1) . , WAL .

+1

All Articles