On 2013-03-29 14:19:59 -0700, Sergey Konoplev wrote:
> On Fri, Mar 29, 2013 at 1:52 PM, anara...@anarazel.de
> <and...@anarazel.de> wrote:
> > I think I See whats going on. Do you still have the datadir available? If 
> > so, could you send the pg_controldata output?
> 
> I have already rebuilt the replica, however below is the output if it is 
> useful:

I have to admit, I find it a bit confusing that so many people report a
bug and then immediately destroy all evidence of the bug. Just seems to
a happen a bit too frequently.

> pg_control version number:            922
> Catalog version number:               201204301
> Database system identifier:           5858109675396804534
> Database cluster state:               in archive recovery
> pg_control last modified:             Сбт 30 Мар 2013 00:21:11
> Latest checkpoint location:           258B/BDBBE748
> Prior checkpoint location:            258B/86DABCB8
> Latest checkpoint's REDO location:    258B/8B78BED0
> Latest checkpoint's TimeLineID:       2
> Latest checkpoint's full_page_writes: on
> Latest checkpoint's NextXID:          0/423386899
> Latest checkpoint's NextOID:          2758636912
> Latest checkpoint's NextMultiXactId:  103920
> Latest checkpoint's NextMultiOffset:  431309
> Latest checkpoint's oldestXID:        225634745
> Latest checkpoint's oldestXID's DB:   16436
> Latest checkpoint's oldestActiveXID:  421766298
> Time of latest checkpoint:            Птн 29 Мар 2013 22:33:01

Thats not a pg_controldata output from the broken replica though, or is
it? I guess its from a new standby?

Andres
Greetings,

Andres Freund

-- 
 Andres Freund                     http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Reply via email to