From: Prashanth Ranjalkar <prashanth.ranjalkar@postgresdba.net>
To: Eduardo Morras <emorrasg@yahoo.es>
Cc: pgsql-admin@postgresql.org
Subject: Re: 9.2.2 - semop hanging
Date: Mon, 15 Jul 2013 19:57:32 +0530
Message-ID: <51E406D4.6080706@postgresdba.net> (raw)
In-Reply-To: <20130715154428.7867d7d74e4cbca04d8b7e4a@yahoo.es>
References: <CAL0i5M7uRMzwEBUZPEdAHto9PcOk1++McMK_wie_njqHCpUSOg@mail.gmail.com>
<20130715154428.7867d7d74e4cbca04d8b7e4a@yahoo.es>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 15-07-2013 19:14, Eduardo Morras wrote:
> On Mon, 15 Jul 2013 10:16:19 -0300
> Rafael Domiciano <rafael.domiciano@gmail.com> wrote:
>
> I'm not a Linux expert, I'm a BSD man, but
>
> a) do you have an interrupt storm?
> b) what does postgres do before the hang?
> c) do you have anyother software running? Including contrib modules. It may be a dns lookup timeout (watch port 53 tcp/udp)
> d) what filesystem? Needs filesystem some kind of "maintenance window"? I mean flush dirty caches, metadata, wake up barriers...
>
>
> --- ---
> Eduardo Morras <emorrasg@yahoo.es>
>
> Max seg size, max total shared memory represents SHMMAX and SHMALL respectively.
max seg size (kbytes) = 83886080
max total shared memory (kbytes) = 17179869184 <tel:17179869184>
At initial glance, I suspect adjusting these values may resolve the
issue as SHMALL should be set either total max memory size or in number
of pages. I think the value set is too large therefore recommend comment
this SHMALL parameter and set only SHMMAX value with 24GB.
Request to verify the server logs if there are any share memory errors
and assume that work_mem value is not set to extreme higher value as the
max connections has set to 500.
/*Thanks & Regards,*/
//**
/*Prashanth Ranjalkar*/
/*Database Consultant & Architect*/
/*Email:prashant.ranjalkar@gmail.com*
<mailto:Email%3Aprashant.ranjalkar@gmail.com>/
/*Skype:prashanth.ranjalkar*/
/*Cell: +91 932 568 2271*/
*/www.postgresdba.net <http://www.postgresdba.net/>/*
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: prashanth.ranjalkar@postgresdba.net, emorrasg@yahoo.es
Subject: Re: 9.2.2 - semop hanging
In-Reply-To: <51E406D4.6080706@postgresdba.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox