Re: could not truncate directory "pg_subtrans": apparent wraparound

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Mikko Partio <mpartio(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
Date: 2010-05-26 06:28:53
Message-ID: 1274855333.6203.2853.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Cédric Villemain 2010-05-26 09:25:59 Re: How to find if a SELECT is reading from buffer or disk ?
Previous Message Mikko Partio 2010-05-26 06:01:41 Re: could not truncate directory "pg_subtrans": apparent wraparound