If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

What were the original values for the configuration variables you edited?

If you return the configuration variables back to their original values, does the error go away?

what is the maximum number of connections configured? as well as the superuser reserved connections?

Last edited by loquin; 01-16-07 at 11:37.

Lou
使大吃一惊"Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
"I have my standards. They may be low, but I have them!" - Bette Middler
"It's a book about a Spanish guy named Manual. You should read it." - Dilbert

shared_buffers = 60000
Per system documentation: "Values of a few thousand are recommended for production installations." Furthermore, "Increasing this parameter may cause PostgreSQL to request more System V shared memory than your operating system's default configuration allows."

The minimum amount is 10 or 2* the maximum number of connections.

You've specified nearly 500 megabytes for shared buffers alone.

I would start with no more than 3-5 thousand for this variable. Increment it a few thousand at a time until you stop seeing any performance gains.

maintenance_work_mem = 120000
This entry is in KB. You've specified 120 megabytes in memory for maintenence operations. This value is probably ok, since usually, only one service that uses maintenence_work_mem will ever be running at any one time. The default value is almost certainly too low for your system.

effective_cache_size = 60000
The only affect this setting will have is on the operation of the query planner. It is an estimate of disk cache that will be available to a single index scan, not a chunk of memory that is reserved. It is factored into the cost of using an index. When this value is high, it's more likely that an index scan will be used; when it's low, it's more likely that a sequential scan will be used.

Probably a good maximum is about 25% of the "available memory" (After the OS and all applications are loaded) for a decent cache size. (NOT 25% of total memory) Note: If this is tuned properly, you won't need to increase shared_buffers unnecessarily.

Lou
使大吃一惊"Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
"I have my standards. They may be low, but I have them!" - Bette Middler
"It's a book about a Spanish guy named Manual. You should read it." - Dilbert