Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5104364FD02 for ; Mon, 3 Nov 2008 11:49:37 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 52099-02 for ; Mon, 3 Nov 2008 11:49:36 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.245]) by mail.postgresql.org (Postfix) with ESMTP id D64B864FE25 for ; Mon, 3 Nov 2008 11:49:36 -0400 (AST) Received: by hs-out-0708.google.com with SMTP id x43so1128540hsb.3 for ; Mon, 03 Nov 2008 07:49:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :sender:to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=sYpuHHUl30kuMcH5dtX+hx3m8JtoPMUwozkKdtcw1i4=; b=TB8zSbA13Y4FgM/YACy71KU5Txh5fH0cZqhiQYn2K2C2ZoY3CATX9wuFBQCGybKKMp ha5v7fKbNw6m1bfnuX9zv7JV1IWk+/HIF2cv6oUqph+EfGeVkbQ6kQdUF4jIFhw+3ZC0 ZNby+fSkjuQ7QtQ0qYdRT9gx8piYN2lQQe128= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references:x-google-sender-auth; b=bgyvAv3rtn0ZBWxDc2kHPh0xet2o2uNWsbeGQA1HjWj8aAj5BVoz9kKxK52k0SAFnn Rgu7lkVzNvuSzFmamHSD4tYm41rmnK4XZAhXeh/eVTox3cfFDpaGhqbUWb9lNTPFjeVG EdgOkOh0byc3qKeyHkWz31LiFINJwY886H0Mc= Received: by 10.64.84.13 with SMTP id h13mr321202qbb.15.1225727374530; Mon, 03 Nov 2008 07:49:34 -0800 (PST) Received: by 10.65.231.9 with HTTP; Mon, 3 Nov 2008 07:49:34 -0800 (PST) Message-ID: <30111ec50811030749h5f2da74bq3d3c071ea26d764a@mail.gmail.com> Date: Mon, 3 Nov 2008 16:49:34 +0100 From: "Matthieu Roger" Reply-To: matthieu.roger@gene6.com To: pgsql-admin@postgresql.org Subject: Re: Crash with pg_clog file not found In-Reply-To: <25898.1225722884@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <30111ec50811022341q688ca946j8269cee93b206a3d@mail.gmail.com> <25898.1225722884@sss.pgh.pa.us> X-Google-Sender-Auth: 1117442cfa08d3bc X-Archive-Number: 200811/12 X-Sequence-Number: 30666 2008/11/3 Tom Lane : > "Matthieu Roger" writes: >> 2008-10-31 20:14:27 CET 10.0.0.119 exile PANIC: could not access >> status of transaction 0 > > Can you present a self-contained test case that causes that? Hello Tom, we were not able to reproduce at will :-( it seems to happen after running for 1 week, sometimes less, always for the same base, I know not helpful at all ... > A stack trace from the PANIC would be mighty useful too, but I dunno > whether there's any point in asking for that from a Windows system. Anyway to do that under windows ? 8.3.3 was also producing the same error, prior version (8.3.1) did not seem to exhibit it, though we've opened a new universe in the web game which increased the number of accounts and players in september so maybe this triggers the problem. I know this is not much helping, if there is any debug build I could run ... Matthieu