Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 247D91337B81 for ; Mon, 9 May 2011 21:55:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 28569-02 for ; Tue, 10 May 2011 00:55:36 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id D91F91337B67 for ; Mon, 9 May 2011 21:55:35 -0300 (ADT) Received: from [192.168.1.3] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LZlbI-1PrzC60H5o-00ltM4; Tue, 10 May 2011 02:55:34 +0200 Message-ID: <4DC88CFF.9020301@2ndquadrant.com> Date: Mon, 09 May 2011 20:55:27 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Richard Broersma CC: pgsql-testers@postgresql.org Subject: Re: 9.1Beta1 - Repeatable Crash on Windows References: <4DC85DF3.9030105@agliodbs.com> <4DC86132.20604@agliodbs.com> <4DC87067.4050101@2ndQuadrant.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:cULBIGT90tnKBAjoFKdZCyY4WyFlDMyz4xK85Cnw2rL wQhLF1Kv5+joa10YG3TfClmw2kdpTS8ZeEuo6iLZHy4ET20Bww +KvPrOHgB62CjVdc/V0v0Y0KSa3r2rC8wQOqoXPDPEDREpAI/1 KSewcwO/7xP4vKAEBFJ3AnGN+by+oWvUtvax9mzjkTVmNhlcqp Kue8HOymmvNwuKv0vVo4FlcEyTpFA1eTPbMg9Qr8cc= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201105/8 X-Sequence-Number: 227 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