Re: could not truncate directory "pg_subtrans": apparent wraparound - Mailing list pgsql-admin

From Simon Riggs
Subject Re: could not truncate directory "pg_subtrans": apparent wraparound
Date
Msg-id 1274855333.6203.2853.camel@ebony
Whole thread Raw
In response to Re: could not truncate directory "pg_subtrans": apparent wraparound  (Mikko Partio <mpartio@gmail.com>)
List 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


pgsql-admin by date:

Previous
From: Mikko Partio
Date:
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
Next
From: Cédric Villemain
Date:
Subject: Re: How to find if a SELECT is reading from buffer or disk ?