Re: gcc 4.6 and hot standby - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: gcc 4.6 and hot standby
Date
Msg-id BANLkTi=U3kA3RdBnykmzq5e_hSQ83Zow6g@mail.gmail.com
Whole thread Raw
In response to Re: gcc 4.6 and hot standby  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: gcc 4.6 and hot standby
List pgsql-hackers
On Wed, Jun 8, 2011 at 12:58, Alex Hunsaker <badalex@gmail.com> wrote:
> On Wed, Jun 8, 2011 at 12:49, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It might be useful to strace the postmaster and walreceiver processes
>> just to see if any signal is actually being sent or received.
>
> Will do.

Find it attached.

Corresponding logs:
2011-06-08 14:01:21 MDT [27779]: [1-1] user= LOG:  could not create
IPv6 socket: Address family not supported by protocol
2011-06-08 14:01:21 MDT [27781]: [1-1] user= LOG:  database system was
shut down in recovery at 2011-06-08 14:00:37 MDT
2011-06-08 14:01:21 MDT [27781]: [2-1] user= LOG:  entering standby mode
2011-06-08 14:01:21 MDT [27781]: [3-1] user= DEBUG:  checkpoint record
is at 86/F6E76708
2011-06-08 14:01:21 MDT [27781]: [4-1] user= DEBUG:  redo record is at
86/F4DF9BF0; shutdown FALSE
2011-06-08 14:01:21 MDT [27781]: [5-1] user= DEBUG:  next transaction
ID: 0/35484525; next OID: 34123294
2011-06-08 14:01:21 MDT [27781]: [6-1] user= DEBUG:  next MultiXactId:
523; next MultiXactOffset: 1046
2011-06-08 14:01:21 MDT [27781]: [7-1] user= DEBUG:  oldest unfrozen
transaction ID: 654, in database 1
2011-06-08 14:01:21 MDT [27781]: [8-1] user= DEBUG:  transaction ID
wrap limit is 2147484301, limited by database with OID 1
2011-06-08 14:01:21 MDT [27781]: [9-1] user= DEBUG:  initializing for
hot standby
2011-06-08 14:01:21 MDT [27781]: [10-1] user= LOG:  redo starts at 86/F4DF9BF0
2011-06-08 14:01:21 MDT [27781]: [11-1] user= LOG:  invalid record
length at 86/F4E62010
2011-06-08 14:01:21 MDT [27783]: [1-1] user= LOG:  streaming
replication successfully connected to primary
2011-06-08 14:01:22 MDT [27781]: [12-1] user= LOG:  invalid record
length at 86/F4E82010
2011-06-08 14:01:24 MDT [27783]: [2-1] user= FATAL:  terminating
walreceiver process due to administrator command
2011-06-08 14:01:24 MDT [27781]: [13-1] user= LOG:  invalid record
length at 86/F4EEC010
2011-06-08 14:01:26 MDT [27784]: [1-1] user= LOG:  streaming
replication successfully connected to primary
2011-06-08 14:01:26 MDT [27781]: [14-1] user= LOG:  invalid record
length at 86/F4F1E010
2011-06-08 14:01:26 MDT [27784]: [2-1] user= FATAL:  terminating
walreceiver process due to administrator command
2011-06-08 14:01:26 MDT [27781]: [15-1] user= LOG:  invalid record
length at 86/F4F22010
2011-06-08 14:01:31 MDT [27785]: [1-1] user= LOG:  streaming
replication successfully connected to primary
^C2011-06-08 14:01:32 MDT [27779]: [2-1] user= LOG:  received fast
shutdown request
2011-06-08 14:01:32 MDT [27785]: [2-1] user= FATAL:  terminating
walreceiver process due to administrator command
2011-06-08 14:01:32 MDT [27782]: [1-1] user= LOG:  shutting down
2011-06-08 14:01:32 MDT [27782]: [2-1] user= LOG:  database system is shut down

Attachment

pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: could not truncate directory "pg_serial": apparent wraparound
Next
From: Pavel Stehule
Date:
Subject: patch for 9.2: enhanced errors