In looking at some cacti memory usage graphs, the Oracle servers show only 6 of a total of16 GB of RAM as 'Total Available'. Whereas, our Postgres version 8.24 servers show all 16 GB of RAM totally available or free. Some people are asking why Postgres doesn't take that memory and lock into it, so you can't see less 'total available' memory. We use a lot of B-tree indexes. This may or may not be related, but it there a good way to make sure those stay in memory?
Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare!
pgsql-admin by date
|Next:||From: Scott Marlowe||Date: 2007-11-14 21:16:26|
|Subject: Re: postgres bogged down beyond tolerance|
|Previous:||From: Tom Lane||Date: 2007-11-14 20:52:17|
|Subject: Re: Error when trying to recover from filesystem backup |