Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id EB8569FB5D6; Mon, 12 Mar 2007 17:55:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 33084-04; Mon, 12 Mar 2007 17:55:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 2F34B9FB50F; Mon, 12 Mar 2007 17:55:06 -0300 (ADT) Received: from [192.168.199.196] (c213-100-160-41.swipnet.se [213.100.160.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id CFA70DCC4EF; Mon, 12 Mar 2007 21:55:04 +0100 (CET) Message-ID: <45F5BE38.6040701@hagander.net> Date: Mon, 12 Mar 2007 21:55:20 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Joost Kraaijeveld CC: Tom Lane , pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] PostgreSQL crashes on Windows 2003 References: <20070312143757.GB9966@svr2.hagander.net> <1173712845.20587.47.camel@panoramix> In-Reply-To: <1173712845.20587.47.camel@panoramix> X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.063 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200703/70 X-Sequence-Number: 24894 Joost Kraaijeveld wrote: >>>> It looks to me that you may be a victim of the bug patched in >>>> >> http://archives.postgresql.org/pgsql-committers/2007-01/msg00214.php. >>>> Tom, whatever happened about a backpatch for that one? >>> It's applied. >>> >> http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/bgwriter.c >> >> Bah. I looked aruond but didn't find it. Clearly I'm blind. Thanks. >> >> So - if you're not on 8.1.7 or 8.1.8, upgrade to 8.1.8 and let us know >> if you still have the problem. > I wrote 8.1.x but we are actually on 8.1.8 and the problem is there (I > just checked because I am not the local system administrator). Just in case, I'd double-check that. Check the version information on postgres.exe (available through the right-click properties view in Explorer). It could be that the upgrade failed. If it's not then the next logical question is - any antivirus, antispyware or quota software running on that machine? //Magnus