Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 6BBC6632DA2
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 24 May 2010 02:46:52 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 48967-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon, 24 May 2010 05:46:45 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-gx0-f227.google.com (mail-gx0-f227.google.com
	[209.85.217.227])
	by mail.postgresql.org (Postfix) with ESMTP id 394376321D3
	for <pgsql-admin@postgresql.org>; Mon, 24 May 2010 02:46:43 -0300 (ADT)
Received: by gxk27 with SMTP id 27so459145gxk.1
	for <pgsql-admin@postgresql.org>; Sun, 23 May 2010 22:46:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:received:in-reply-to
	:references:date:message-id:subject:from:to:cc:content-type;
	bh=ItnE1O6Eru3Yqc8uj4/XamPcAqUC82WRTeCD3j2Kl/g=;
	b=vw6gGHN/7UsgfVAO3vnWpERCpfCd8s8E4trAG+naTYJOnklVaRp+evXOC5kQXgZMMm
	92yTz2ofxf7/N4+7wBS4wRK4AZ9KzlRne5X9HRvARpg6Kmp8dIY0JytbTJ3kZEkqKGcc
	0DOQpaT3xhfvhNSiopSVjtpmfDxRoKtLPjI94=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=EoNOeEc0Z9QPPexlXCZB61GpNipMbfE5cLqWGdizPGkRx9Ntww4DFnuUCN0/KQbuYc
	GiKNhVzmxvtrBtxnMAuMvbdP971V9WC/u4IKTwnoHLicIS7jXz+I8pcj7XewEbAT4Rxj
	+OlZ3e+JTuLi7l5Jxf0RaQSA3+jEmtwV823/Q=
MIME-Version: 1.0
Received: by 10.101.5.30 with SMTP id h30mr6062287ani.86.1274680002996; Sun,
	23 May 2010 22:46:42 -0700 (PDT)
Received: by 10.100.121.12 with HTTP; Sun, 23 May 2010 22:46:42 -0700 (PDT)
In-Reply-To: <18038.1274637760@sss.pgh.pa.us>
References: <AANLkTikGI8SwkoNXUHyRFrwqbJufKlFS6UrzZEtp8Yt9@mail.gmail.com>
	<18038.1274637760@sss.pgh.pa.us>
Date: Mon, 24 May 2010 08:46:42 +0300
Message-ID: <AANLkTilSLidcJIl8feLS9bMFoGdpq0noOffO21o8RTyo@mail.gmail.com>
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
From: Mikko Partio <mpartio@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Content-Type: multipart/alternative; boundary=005045015d83c7e908048750905d
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.899 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001
X-Spam-Level: 
X-Archive-Number: 201005/219
X-Sequence-Number: 34692

--005045015d83c7e908048750905d
Content-Type: text/plain; charset=ISO-8859-1

On Sun, May 23, 2010 at 9:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Mikko Partio <mpartio@gmail.com> writes:
> > got the following line at postgresql log:
>
> > May 16 01:17:35 xxx postgres[25550]: [1-1] LOG:  could not truncate
> > directory "pg_subtrans": apparent wraparound
>
> >  PostgreSQL 9.0beta1 on x86_64-unknown-linux-gnu, compiled by GCC gcc
> (GCC)
> > 4.1.2 20080704 (Red Hat 4.1.2-46), 64-bit
>
> Where did this beta1 installation come from --- was it freshly initdb'd
> under 9.0, or did you use pg_upgrade on a pre-existing database that had
> been around for awhile?  It strikes me that the recently identified bug
> in pg_upgrade about not fixing the datfrozenxid of template0 might
> possibly explain this.  You'd need to have upgraded an installation that
> was at least a couple billion transactions old to hit that bug.
>


It was freshly initdb'd with beta1 binaries, the contents were loded from a
pg_dump file. The number of transactions is very small, we're talking about
thousands (not billions). This database is the master of a hot standby
installation, if that matters.

Regards

Mikko

--005045015d83c7e908048750905d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Sun, May 23, 2010 at 9:02 PM, Tom Lan=
e <span dir=3D"ltr">&lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa=
.us</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">Mikko Partio &lt;<a href=3D"mailto:mpartio@gmail.com">mpa=
rtio@gmail.com</a>&gt; writes:<br>
</div><div class=3D"im">&gt; got the following line at postgresql log:<br>
<br>
&gt; May 16 01:17:35 xxx postgres[25550]: [1-1] LOG: =A0could not truncate<=
br>
&gt; directory &quot;pg_subtrans&quot;: apparent wraparound<br>
<br>
</div><div class=3D"im">&gt; =A0PostgreSQL 9.0beta1 on x86_64-unknown-linux=
-gnu, compiled by GCC gcc (GCC)<br>
&gt; 4.1.2 20080704 (Red Hat 4.1.2-46), 64-bit<br>
<br>
</div>Where did this beta1 installation come from --- was it freshly initdb=
&#39;d<br>
under 9.0, or did you use pg_upgrade on a pre-existing database that had<br=
>
been around for awhile? =A0It strikes me that the recently identified bug<b=
r>
in pg_upgrade about not fixing the datfrozenxid of template0 might<br>
possibly explain this. =A0You&#39;d need to have upgraded an installation t=
hat<br>
was at least a couple billion transactions old to hit that bug.<br></blockq=
uote><div><br></div><div><br></div><div>It was freshly initdb&#39;d with be=
ta1 binaries, the contents were loded from a pg_dump file. The number of tr=
ansactions is very small, we&#39;re talking about thousands (not billions).=
 This database is the master of a hot standby installation, if that matters=
.</div>
<div><br></div><div>Regards</div><div><br></div><div>Mikko</div></div>

--005045015d83c7e908048750905d--