Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL 9.0.4 crashing

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: "R, Abhilash (HP Software)" <abhilash(dot)r(at)hp(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL 9.0.4 crashing
Date: 2012-06-01 14:52:59
Message-ID: CAOR=d=0eKRJGUoeHYjCYr+_xZDo-b8Q-eLq=N2cZdGpzj14GAA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
What's work_mem and maintenance_work_mem set to?

On Thu, May 31, 2012 at 10:30 PM, R, Abhilash (HP Software)
<abhilash(dot)r(at)hp(dot)com> wrote:
> It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB.
>
> I could see windows Resource-Exhaustion Detector errors in event viewer saying - " Windows successfully diagnosed a low virtual memory condition." around the time when postgreSQL crashed. Can this cause the crash?
>
> shared_buffers = 32MB
>
> It's a 64 bit box.
>
> Regards,
> Abhilash R
>
> -----Original Message-----
> From: Merlin Moncure [mailto:mmoncure(at)gmail(dot)com]
> Sent: Friday, June 01, 2012 2:45 AM
> To: R, Abhilash (HP Software)
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] PostgreSQL 9.0.4 crashing
>
> On Thu, May 31, 2012 at 4:57 AM, R, Abhilash (HP Software)
> <abhilash(dot)r(at)hp(dot)com> wrote:
>> PostgreSQL 9.0.4 is crashing intermittently in Windows 2008 R2 environment
>> with following error in log file.
>>
>>
>>
>> 2012-05-31 03:15:54 IST LOG:  server process (PID 49972) was terminated by
>> exception 0xC000012D
>>
>> 2012-05-31 03:15:54 IST HINT:  See C include file "ntstatus.h" for a
>> description of the hexadecimal value.
>>
>> 2012-05-31 03:15:54 IST LOG:  terminating any other active server processes
>>
>> 2012-05-31 03:15:54 IST WARNING:  terminating connection because of crash of
>> another server process
>>
>> 2012-05-31 03:15:54 IST DETAIL:  The postmaster has commanded this server
>> process to roll back the current transaction and exit, because another
>> server process exited abnormally and possibly corrupted shared memory.
>>
>> 2012-05-31 03:15:54 IST HINT:  In a moment you should be able to reconnect
>> to the database and repeat your command.
>>
>> 2012-05-31 03:15:54 IST WARNING:  terminating connection because of crash of
>> another server process
>>
>>
>>
>> I could find a related, known issue with 8.3.9 with ref. 5965; Is  this
>> issue fixed in 9.0.4?
>
> After some googling I'm seeing some hints that you may have
> overcommitted virtual memory.  How much memory do you have and what's
> shared buffers set to?  Is this 32/64 bit?
>
> merlin
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general



-- 
To understand recursion, one must first understand recursion.

In response to

Responses

pgsql-general by date

Next:From: SambaDate: 2012-06-01 15:16:24
Subject: Re: Disable Streaming Replication without restarting either master or slave
Previous:From: Tom LaneDate: 2012-06-01 13:52:59
Subject: Re: pg_upgrade from 9.0.7 to 9.1.3: duplicate key pg_authid_oid_index

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group