Re: Hot Standby (commit fest version - v5)

On Thu, Nov 20, 2008 at 8:15 PM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>wrote:

>
>
> On Thu, Nov 20, 2008 at 7:50 PM, Simon Riggs <simon(at)2ndquadrant(dot)com>wrote:
>
>
>
>>
>> (I assume you mean bgwriter, not archiver process).
>>
>>
> Yeah, its the bgwriter, IIRC hung while taking checkpoint.
>
>
>
Sorry, its the startup process thats stuck in the checkpoint. Here is the
stack trace:

(gdb) bt
#0 0x00110402 in __kernel_vsyscall ()
#1 0x0095564b in semop () from /lib/libc.so.6
#2 0x0825c703 in PGSemaphoreLock (sema=0xb7c52c7c, interruptOK=0 '\0') at
pg_sema.c:420
#3 0x0829ff5e in LWLockAcquire (lockid=WALInsertLock, mode=LW_EXCLUSIVE) at
lwlock.c:456
#4 0x080d5c7e in XLogInsert (rmid=0 '\0', info=16 '\020', rdata=0xbfda1798)
at xlog.c:746
#5 0x080e2e0f in CreateCheckPoint (flags=6) at xlog.c:6674
#6 0x080e1afd in StartupXLOG () at xlog.c:6077
#7 0x08104f2f in AuxiliaryProcessMain (argc=2, argv=0xbfda19e4) at
bootstrap.c:421
#8 0x0826d285 in StartChildProcess (type=StartupProcess) at
postmaster.c:4104
#9 0x082690d9 in PostmasterMain (argc=3, argv=0x9c89a60) at
postmaster.c:1034
#10 0x081f90ff in main (argc=3, argv=0x9c89a60) at main.c:188

ISTM that the postmaster somehow does not receive (may be because of what I
reported in my other mail) PMSIGNAL_RECOVERY_START and hence bgwriter is not
started. The startup process then itself tries to take a checkpoint and
hangs.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com