858 reputation
46
bio website
location Amsterdam, The Netherlands
age
visits member for 4 years, 9 months
seen Apr 27 at 9:32

alt text

CTO


May
27
comment How to make schema dumps comparable between Windows and Linux
And did you use the same pg_dump-version to create the backups? pg_dump version 8.4 can also create backups of an 8.2-database. Using different databases is asking for trouble, an 8.4-backup might not work in a 8.2-databaseserver. Be careful!
May
26
answered How to make schema dumps comparable between Windows and Linux
Apr
5
answered Cant connect to MySQL server from Java application
Apr
2
comment How to optimize a postgreSQL server for a “write once, read many”-type infrastructure?
auto_vacuum can play a role, it has to analyze your data and clean up deleted data. The correct indexes will help the SELECTs (and maybe the DELETE's), inserting using prepared statements or COPY can give a hugh performance boost on the inserts. There are many options and it all depends on you usage patern. So, start testing!
Apr
1
answered How to optimize a postgreSQL server for a “write once, read many”-type infrastructure?
Mar
25
awarded  Supporter
Mar
23
awarded  Teacher
Mar
23
comment PostgreSQL lots of large Arrays and Writes
See this picture: postgresql.org/files/documentation/books/aw_pgsql/… And yes, the 58GB is all the cache. PostgreSQL doesn't take all shared_buffers when it starts, it just takes what it needs, up to the limits set in the configuration.
Mar
22
answered postgres memory allocation tuning 2
Mar
22
comment PostgreSQL lots of large Arrays and Writes
Because you don't want to kill your server. If you have a lot of RAM, you might use more than 25% for shared_buffers, but be carefull. Be very carefull! PostgreSQL is using more RAM than just shared_buffers and your server also needs RAM for other things. Every connection needs RAM, every sort operation needs RAM, etc. etc. etc. When you push it too much, your server might kill the postmaster (eats too much RAM) or starts swapping and killing performance. A better queryplan, using less RAM, might be a better idea. But that's up to the database.
Mar
22
answered PostgreSQL lots of large Arrays and Writes