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

Assertion failure at standby promotion

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Assertion failure at standby promotion
Date: 2013-05-03 15:17:42
Message-ID: CAHGQGwEO1GF3=7LAeyn630+PNjjkC4fnwqx_L_Vyq6Y+OsB5jg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

I got the following assertion failure when I promoted the standby.

2013-05-04 00:12:31 JST sby1 LOG:  received promote request
2013-05-04 00:12:31 JST sby1 FATAL:  terminating walreceiver process
due to administrator command
2013-05-04 00:12:31 JST sby1 LOG:  redo done at 0/6FFE038
2013-05-04 00:12:31 JST sby1 LOG:  last completed transaction was at
log time 2013-05-04 00:12:25.878909+09
2013-05-04 00:12:31 JST sby1 LOG:  selected new timeline ID: 2
2013-05-04 00:12:31 JST sby1 LOG:  archive recovery complete
2013-05-04 00:12:31 JST sby1 LOG:  checkpoint starting:
TRAP: FailedAssertion("!(sentPtr <= sendTimeLineValidUpto)", File:
"walsender.c", Line: 1465)
2013-05-04 00:12:31 JST sby1 LOG:  autovacuum launcher started

The way to reproduce this is:

1. Create one master A, one standby B, and one cascade standby C.
2. Run pgbench -i -s 10
3. Promote the standby B before pgbench -i finishes

Regards,

-- 
Fujii Masao


Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2013-05-03 15:24:54
Subject: Re: Remaining beta blockers
Previous:From: C├ędric VillemainDate: 2013-05-03 15:13:05
Subject: Re: Recovery target 'immediate'

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