Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125])
	by mail.postgresql.org (Postfix) with ESMTP id 2BDF51C0B196
	for <pgsql-admin@postgresql.org>; Fri, 20 Jul 2012 01:38:56 -0300 (ADT)
Received: from mail-pb0-f46.google.com ([209.85.160.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ringerc@ringerc.id.au>) id 1Ss4zP-0002O2-8o
	for pgsql-admin@postgresql.org; Fri, 20 Jul 2012 04:38:56 +0000
Received: by pbbrp8 with SMTP id rp8so5512445pbb.19
	for <pgsql-admin@postgresql.org>; Thu, 19 Jul 2012 21:38:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:x-gm-message-state;
	bh=Y0yT49Pi1kXuYenLE1ktD3AsQGdm9y6CdZQl6duqAMc=;
	b=ZaSi/IE8hYbR/SsZlfeyEa6XdpSl8cVJztRCxgvKHp4dO/6mdaXKIAt3aKu8tApmPA
	hMnU90p+8ZNnNzn9SOL2t0v2Ilan21wgvCaV65IA5ahPt2cSY1DdaWcH3qRJhc/nAkUQ
	EDWvGrgKcXNvG+2vtsJCS/YHAGKHulMAEBSpZ5Xc4w+ZWTUTGg/eEXgWT5qiO4JXClyL
	z5UooCM6ioa2aGfRtyeRIyOd3xXx60iUd5cauvsM2QDXLmiosxmUUMqEfrtTVT6PZtK6
	c+CoQJDBCykaUcB+mdamX9XMYlj4W/eXOusJMaVfN2UTBdxOXpZd3soBDByT2jfwBBKU
	MZFQ==
Received: by 10.68.217.37 with SMTP id ov5mr10641612pbc.12.1342759122089;
	Thu, 19 Jul 2012 21:38:42 -0700 (PDT)
Received: from ayaki.localdomain (58-7-231-93.dyn.iinet.net.au. [58.7.231.93])
	by mx.google.com with ESMTPS id
	ns5sm3142828pbb.26.2012.07.19.21.38.39 (version=SSLv3 cipher=OTHER);
	Thu, 19 Jul 2012 21:38:41 -0700 (PDT)
Message-ID: <5008E0CC.9020107@ringerc.id.au>
Date: Fri, 20 Jul 2012 12:38:36 +0800
From: Craig Ringer <ringerc@ringerc.id.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: Umer Asghar <umerasghar@gmail.com>
CC: pgsql-admin@postgresql.org
Subject: Re: Postgres Database got down
References: <000901cd65ca$4eb7cd00$ec276700$@com>
In-Reply-To: <000901cd65ca$4eb7cd00$ec276700$@com>
Content-Type: multipart/alternative;
	boundary="------------030909050703020200070000"
X-Gm-Message-State: 
 ALoCoQkUDPrzli7TElmxhGCkgjjbmKMJbuOHsge+04EF5TEaDLMgu5zwJggVDO3/yVLBMkb4W5w0
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201207/54
X-Sequence-Number: 39771

This is a multi-part message in MIME format.
--------------030909050703020200070000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/20/2012 12:19 AM, Umer Asghar wrote:
>  After that I gave it a reboot to my machine, and its 3 hrs now and 
> its running fine. but not sure why it got down and will it go down 
> again soon.
>
> Can somebody advice what should I looked into?
>
> [snip]
>
> 2012-07-19 18:05:08 PKT LOG:  server process (PID 1836) exited with 
> exit code 128
>

Maybe this?

http://support.microsoft.com/kb/974509

Thankyou for including your logs without having to be asked. It's 
usually helpful if you also provide your PostgreSQL version and 
architecture (x86 or x64) - but in this case I don't think it matters as 
it seems to be a Windows issue.

--
Craig Ringer

--------------030909050703020200070000
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/20/2012 12:19 AM, Umer Asghar
      wrote:<br>
    </div>
    <blockquote cite="mid:000901cd65ca$4eb7cd00$ec276700$@com"
      type="cite">
      <div>&nbsp;After that I gave it a reboot to my machine, and its 3 hrs
        now and its running fine. but not sure why it got down and will
        it go down again soon.
        <p>Can somebody advice what should I looked into? </p>
        [snip]<br>
        <p><span>2012-07-19 18:05:08 PKT LOG:&nbsp; server process (PID 1836)
            exited with exit code 128</span><br>
        </p>
      </div>
    </blockquote>
    <br>
    Maybe this?<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="http://support.microsoft.com/kb/974509">http://support.microsoft.com/kb/974509</a><br>
    <br>
    Thankyou for including your logs without having to be asked. It's
    usually helpful if you also provide your PostgreSQL version and
    architecture (x86 or x64) - but in this case I don't think it
    matters as it seems to be a Windows issue.<br>
    <br>
    --<br>
    Craig Ringer<br>
  </body>
</html>

--------------030909050703020200070000--