Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
From: Simon Riggs <simon@2ndQuadrant.com>
To: Mikko Partio <mpartio@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-admin@postgresql.org
In-Reply-To: <AANLkTilMgQHt9h4lO_Nj8j32bQtEWNuogt4vEbNkce6B@mail.gmail.com>
References: <AANLkTikGI8SwkoNXUHyRFrwqbJufKlFS6UrzZEtp8Yt9@mail.gmail.com>
	<18038.1274637760@sss.pgh.pa.us>
	<AANLkTilSLidcJIl8feLS9bMFoGdpq0noOffO21o8RTyo@mail.gmail.com>
	<1274730957.6203.527.camel@ebony>
	<AANLkTilMgQHt9h4lO_Nj8j32bQtEWNuogt4vEbNkce6B@mail.gmail.com>
Content-Type: text/plain
Date: Wed, 26 May 2010 07:28:53 +0100
Message-Id: <1274855333.6203.2853.camel@ebony>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2010-05-26 at 09:01 +0300, Mikko Partio wrote:

> With this database instance (beta1 initdb'd) I have not made
> failovers. I don't think I have any special hot standby parameters
> either. 

OK, so that pretty much rules out HS as a direct cause.

> Non-default hot standby related configuration options (master
> database):
> 
> 
> wal_level = hot_standby         # minimal, archive, or hot_standby
> archive_mode = on               # allows archiving to be done
> archive_command = '/postgresql/bin/archive_wal.sh "%p" "%f"'
>    # command to use to archive a logfile segment
> archive_timeout = 3600          # force a logfile segment switch after
> this
> hot_standby = off               # allows queries during recovery
> max_wal_senders = 3             # max number of walsender processes
> wal_keep_segments = 10          # in logfile segments, 16MB each; 0
> disables

-- 
 Simon Riggs           www.2ndQuadrant.com