Home/ Questions/Q 6681669
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T04:36:58+00:00

All, I am running CentOS 6.0 with Postgresql 8.4 and can’t seem to figure

  • 0

All,

I am running CentOS 6.0 with Postgresql 8.4 and can’t seem to figure out how to prevent so much disc swap from occurring. I have 12 gigs of RAM and 4 processors and I am doing some simple updates (1 table at a time). I thought for a minute that the inserts happening in parallel from a script I wrong was causing the large memory usage but when I saw the simple update causing it too I basically threw in the towel and decided to ask for help.

I pasted the conf file here. http://pastebin.com/e0jdBu0J

You can see that I set the buffers relatively low and the connection amounts high. The DB service will not start if I set the shared buffers any higher than 64 megs. Anyone have an idea what may be causing this for me?

Thanks,
Adam

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you’re going into swap, increasing shared_buffers will make the problem worse; you’ll be taking RAM away from the part that’s running out and swapping, instead dedicating memory to the database caching. It’s worth fixing SHMMAX etc. just on general principle and for later tuning work, but that’s not going to help with this problem.

    Guessing at the identify of your memory gobbling source is a crapshoot. Far better to look at data from “top -c” and ps to find which processes are using a lot of it. It’s possible for a really bad query to consume way more memory than it should. If you see memory use spike up for a PostgreSQL process running something, check the process ID against the information in pg_stat_tables to see what it’s doing.

    There are a couple of things that can cause this sort of issue that often surprise people. If you are doing a large number of row updates in a single transaction, and there are foreign key checks or triggers involved, that can run out of memory. The queue of things to check in each of those cases is kept in RAM, and can be surprisingly big.

    There are two problems with your PostgreSQL settings that might be related. Databases don’t actually work very well if you have a lot more active connections than cores in the server; best performance is normally 2 to 3 active clients per core. And all sorts of things go wrong once you’ve got more than a few hundred connection. There is some connections^2 behavior that gets ugly there performance wise, and there are some memory issues too. If you really need 1250 connections, you should be using a connection pooler such as pgBouncer or pgpool-II.

    And effective_io_concurrency = 1000 is way too high for any hardware on the planet. Useful values for that in a small multiple of how many disks you have in the server. I have no idea what happens as far as memory usage goes when you set it that high, but it’s not been tested very well at that range. Normal settings more like 1 to 25. The parameters outlined at Tuning Your PostgreSQL Server are much more important than it is; the concurrency value only impacts one particular type of table scan.

    • 0