Re: FATAL: the database system is starting up

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: FATAL: the database system is starting up
Date: 2011-12-05 12:07:20
Message-ID: CADK3HH+=vXBVyXRgtDQC5Ot7vSVPdu9X7Gr55d0oqFPDThU-SQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Answering my own question ....

hot_standby = off by default..

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On Mon, Dec 5, 2011 at 6:43 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> This is the second hot_standby server that I have setup for this
> particular master server. The logs look good
>
> 2011-12-05 06:27:36 EST user=,db= [2065] LOG:  database system was
> interrupted; last known up at 2011-12-05 06:16:22 EST
> 2011-12-05 06:27:36 EST user=,db= [2065] LOG:  entering standby mode
> 2011-12-05 06:27:43 EST user=,db= [2065] LOG:  restored log file
> "00000001000000120000003C" from archive
> 2011-12-05 06:27:43 EST user=,db= [2065] LOG:  redo starts at 12/3C000020
> 2011-12-05 06:27:43 EST user=,db= [2065] LOG:  consistent recovery
> state reached at 12/3D000000
> scp: walfiles/ca05db01/00000001000000120000003D: No such file or directory
> 2011-12-05 06:27:45 EST user=,db= [2077] LOG:  streaming replication
> successfully connected to primary
> 2011-12-05 06:28:38 EST user=postgres,db=postgres [2089] FATAL:  the
> database system is starting up
>
>
>
> It never gets to the point where it says it is ready to accept connections ?
>
>
> pg_control data is identical to the other slave
>
> pg_control version number:            903
> Catalog version number:               201008051
> Database system identifier:           5673024330384732158
> Database cluster state:               in archive recovery
> pg_control last modified:             Mon Dec  5 06:37:43 2011
> Latest checkpoint location:           12/3E000058
> Prior checkpoint location:            12/3D008628
> Latest checkpoint's REDO location:    12/3E000020
> Latest checkpoint's TimeLineID:       1
> Latest checkpoint's NextXID:          0/34511
> Latest checkpoint's NextOID:          23996630
> Latest checkpoint's NextMultiXactId:  1
> Latest checkpoint's NextMultiOffset:  0
> Latest checkpoint's oldestXID:        654
> Latest checkpoint's oldestXID's DB:   1
> Latest checkpoint's oldestActiveXID:  34511
> Time of latest checkpoint:            Mon Dec  5 06:36:22 2011
> Minimum recovery ending location:     12/3D008680
> Backup start location:                0/0
> Current wal_level setting:            hot_standby
> Current max_connections setting:      210
> Current max_prepared_xacts setting:   0
> Current max_locks_per_xact setting:   64
> Maximum data alignment:               8
> Database block size:                  8192
> Blocks per segment of large relation: 131072
> WAL block size:                       8192
> Bytes per WAL segment:                16777216
> Maximum length of identifiers:        64
> Maximum columns in an index:          32
> Maximum size of a TOAST chunk:        1996
> Date/time type storage:               64-bit integers
> Float4 argument passing:              by value
> Float8 argument passing:              by value
>
>
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Sullivan 2011-12-05 12:43:45 Re: Regarding licensing of Postgresql
Previous Message Dave Cramer 2011-12-05 11:43:00 FATAL: the database system is starting up