| From: | hubert depesz lubaczewski <depesz(at)gmail(dot)com> |
|---|---|
| To: | "Anand Kumar, Karthik" <Karthik(dot)AnandKumar(at)classmates(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Repeated semop calls |
| Date: | 2014-06-27 07:15:23 |
| Message-ID: | CAKrjmhdXhj5gp5jKT2sdmZS3CeagLSSHMXaknvF5EDn+iGNAvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 26, 2014 at 10:03 PM, Anand Kumar, Karthik <
Karthik(dot)AnandKumar(at)classmates(dot)com> wrote:
> 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)
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rémi Cura | 2014-06-27 08:18:08 | Re: python modul pre-import to avoid importing each time |
| Previous Message | Atri Sharma | 2014-06-27 06:27:23 | Re: Executing nodenestloop.c |