Re: Repeated semop calls
| От | hubert depesz lubaczewski |
|---|---|
| Тема | Re: Repeated semop calls |
| Дата | |
| Msg-id | CAKrjmhdXhj5gp5jKT2sdmZS3CeagLSSHMXaknvF5EDn+iGNAvg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Repeated semop calls ("Anand Kumar, Karthik" <Karthik.AnandKumar@classmates.com>) |
| Ответы |
Re: Repeated semop calls
|
| Список | pgsql-general |
On Thu, Jun 26, 2014 at 10:03 PM, Anand Kumar, Karthik <Karthik.AnandKumar@classmates.com> wrote:
2. disabling transparent hugepage support - this has various names on different kernel/distributions, but "find /sys | grep -i transparent.*hugepage.*enable" will find it, and then just echo never there.
depesz
We run postgres 9.3.3 on Centos 6.3, kernel 2.6.32-431.3.1. Every once in a while, we see postgres processes spinning on semop:
it might be long shot, but when we had problems with lots of backends "sitting" in semop, it was solved by:
1. disabling zone_reclaim (echo 0 > /proc/sys/vm/zone_reclaim_mode)В списке pgsql-general по дате отправления: