Re: 8.1.2 postmaster died

Have a look at "16.4.3. Linux Memory Overcommit" on
http://www.postgresql.org/docs/8.1/interactive/kernel-resources.html

Thanks,
------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 11/9/06, Talha Khan <talha(dot)amjad(at)gmail(dot)com> wrote:
>
> Hi Ed,
>
> I don't think its pgsql thats sending the SIGKILL its being done by the
> OS. The reason can only be confirmed after looking at your log files but the
> probability is that your OS ran out of memory and in order to protect itself
> it had to kill the processes that were taking a lot of memory thus ended up
> killing pgsql processes. Its just a hunch that i have but the reason can
> only be confirmed after seeing your logs.
>
> Regards
> Talha Khan
>
> On 11/9/06, Ed Loehr <ed(at)loehrtech(dot)com> wrote:
> >
> > On Wednesday November 8 2006 12:30 pm, Shoaib Mir wrote:
> > > To be specific you need to look at the syslogs to see if it
> > > was actually some OOM killer or not.
> >
> > I checked all db logs + syslog, of course. All they show is the
> > process receiving SIGKILL (followed by all others being shutdown
> > as a result).
> >
> > Is there any circumstance at all under which pgsql itself would
> > issue a sigkill to one of the backends?
> >
> > Ed
> >
>
>