Skip site navigation (1) Skip section navigation (2)

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: MirrorX <mirrorx(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: could not truncate directory "pg_subtrans": apparent wraparound
Date: 2011-12-13 21:08:54
Message-ID: CA+TgmoaFEjr5zCosiQSJ+SfVbzBginiREW5TrZ1aVeSCxiEB3w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Sun, Dec 4, 2011 at 7:27 AM, MirrorX <mirrorx(at)gmail(dot)com> wrote:
> hello to all,
>
> i found this error in the logs on the hot_standby server. this error
> appeared only once a few days back and hasn't come up again. the version i
> am using is 9.0.5 and the primary was loaded by restoring dump files
> (previous version was 8.4.4). i have never switched to this server and i am
> using streaming replication. the activity of the primary is very low, it
> creates about 5-10 wal archives every day and has always been like that. the
> error does not appear on the primary.
>
>  if you need more details about the servers plz tell me and i will post
> them.any information that you may have is more than welcome. thx in advance

Could you send the output of pg_controldata on the standby, and also
the contents of pg_clog on that machine?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: John LumbyDate: 2011-12-13 21:30:47
Subject: Re: LIKE predicate and ERROR: 42P22: could not determine which collation to use for string comparison - HINT: Use the COLLATE clause ...
Previous:From: Robert HaasDate: 2011-12-13 20:56:37
Subject: Re: BUG #6317: sequence error for pg_dump

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group