Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1216B9FB33F; Mon, 12 Mar 2007 11:38:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 46487-04; Mon, 12 Mar 2007 11:37:53 -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 0528F9FB272; Mon, 12 Mar 2007 11:37:59 -0300 (ADT) Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by svr2.hagander.net (Postfix) with ESMTP id 39499DCC683; Mon, 12 Mar 2007 15:37:57 +0100 (CET) Received: by svr2.hagander.net (Postfix, from userid 1000) id 36CC0DCC685; Mon, 12 Mar 2007 15:37:57 +0100 (CET) Date: Mon, 12 Mar 2007 15:37:57 +0100 From: Magnus Hagander To: Tom Lane Cc: Joost Kraaijeveld , pgsql-general@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [GENERAL] PostgreSQL crashes on Windows 2003 Message-ID: <20070312143757.GB9966@svr2.hagander.net> References: <20070312133933.GE8325@svr2.hagander.net> <1173707182.20587.34.camel@panoramix> <20070312135617.GA9966@svr2.hagander.net> <15029.1173708828@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15029.1173708828@sss.pgh.pa.us> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.058 tagged_above=0 required=5 tests=AWL, BAYES_50 X-Spam-Level: X-Archive-Number: 200703/65 X-Sequence-Number: 24889 On Mon, Mar 12, 2007 at 10:13:48AM -0400, Tom Lane wrote: > Magnus Hagander writes: > > 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. //Magnus