Re: BUG #12617: DETAIL: Could not read from file "pg_subtrans/06F8" at offset 90112: Success. - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #12617: DETAIL: Could not read from file "pg_subtrans/06F8" at offset 90112: Success.
Date
Msg-id 20150121150712.GR1663@alvh.no-ip.org
Whole thread Raw
In response to BUG #12617: DETAIL: Could not read from file "pg_subtrans/06F8" at offset 90112: Success.  (davividal@gmail.com)
Responses Re: BUG #12617: DETAIL: Could not read from file "pg_subtrans/06F8" at offset 90112: Success.
List pgsql-bugs
davividal@gmail.com wrote:

> My scenario: I have a daily physical backup from my production server
> (9.1).
> I create a 9.1 cluster from it and upgrade it to 9.4 daily. After that, I
> deploy a bunch of changes using sqitch (sqitch.org). Again: I do it on a
> daily basis, but this is the first time I faced this issue:
>
> $ sqitch deploy -t sandbox views/sistema.sf_guard_user@HEAD
> Deploying changes through views/sistema.sf_guard_user to sandbox
>   + data_migration/rate_plan.payment_policies ...............
> psql:sql/deploy/data_migration/rate_plan.payment_policies.sql:21: ERROR:
> could not access status of transaction 116940611
> DETAIL:  Could not read from file "pg_subtrans/06F8" at offset 90112:
> Success.
> CONTEXT:  while updating tuple (6302,20) in relation "rate_daily_policies"
> not ok

Can you please paste the output of pg_controldata on both clusters?


--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: Pedro Gimeno
Date:
Subject: Re: BUG #12589: Poor randomness from random() with some seeds; poor resolution
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade failure on Windows Server