pg.ddx.io  pgsql-testers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <greg@2ndquadrant.com>
To: Richard Broersma <richard.broersma@gmail.com>
Cc: pgsql-testers@postgresql.org
Subject: Re: 9.1Beta1 - Repeatable Crash on Windows
Date: Mon, 09 May 2011 20:55:27 -0400
Message-ID: <4DC88CFF.9020301@2ndquadrant.com> (raw)
In-Reply-To: <BANLkTi=JcpNNEZafZFdLYBqMpOFi_kB57w@mail.gmail.com>
References: <BANLkTikq8DrkJho-533tHRq3uDc9kjQrNQ@mail.gmail.com>
	<4DC85DF3.9030105@agliodbs.com>
	<BANLkTi=Z6M2CbFGrrxqyVZZp4q4Ugho6ZQ@mail.gmail.com>
	<4DC86132.20604@agliodbs.com>
	<4DC87067.4050101@2ndQuadrant.com>
	<BANLkTi=JcpNNEZafZFdLYBqMpOFi_kB57w@mail.gmail.com>

Richard Broersma wrote:
> Here is what the logs show:
>
> 2011-05-09 07:49:37 PDT LOG:  server process (PID 2848) was terminated
> by exception 0xC0000005
>   

Too bad, that's just a generic "accessed memory you shouldn't have" 
exception.  Not much help narrowing down the source.  That could be a 
driver or hardware issue, but since you say it's repeatable that seems 
less likely.

At this point, fork in the road.  If someone else can reproduce this on 
another Windows system, they may be able to run with it.  But if you can 
spare some time to dig further, the instructions at 
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows 
go over how to trace into where it's actually failing at yourself.  If 
you run PostgreSQL on Windows, that's good defensive practice to fit in 
on a day it's not an emergency to do so.  (The same is true of any 
platform, it just takes more time to setup on Windows)

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us





view thread (19+ messages)  latest in thread

Message-ID: <4DC88CFF.9020301@2ndquadrant.com>
Permalink:  ../4DC88CFF.9020301@2ndquadrant.com/
Also on:    postgresql.org/message-id/4DC88CFF.9020301@2ndquadrant.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-testers@postgresql.org
  Cc: greg@2ndquadrant.com, richard.broersma@gmail.com
  Subject: Re: 9.1Beta1 - Repeatable Crash on Windows
  In-Reply-To: <4DC88CFF.9020301@2ndquadrant.com>
  References: <BANLkTikq8DrkJho-533tHRq3uDc9kjQrNQ@mail.gmail.com> <4DC85DF3.9030105@agliodbs.com> <BANLkTi=Z6M2CbFGrrxqyVZZp4q4Ugho6ZQ@mail.gmail.com> <4DC86132.20604@agliodbs.com> <4DC87067.4050101@2ndQuadrant.com> <BANLkTi=JcpNNEZafZFdLYBqMpOFi_kB57w@mail.gmail.com> <4DC88CFF.9020301@2ndquadrant.com>

* 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