From: Mikko Partio <mpartio@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
Date: Mon, 24 May 2010 08:46:42 +0300
Message-ID: <AANLkTilSLidcJIl8feLS9bMFoGdpq0noOffO21o8RTyo@mail.gmail.com> (raw)
In-Reply-To: <18038.1274637760@sss.pgh.pa.us>
References: <AANLkTikGI8SwkoNXUHyRFrwqbJufKlFS6UrzZEtp8Yt9@mail.gmail.com>
<18038.1274637760@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mpartio@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
In-Reply-To: <AANLkTilSLidcJIl8feLS9bMFoGdpq0noOffO21o8RTyo@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox