this is the stack trace
thx in advance :D
$ ps aux | grep 4500
postgres 4500 4.2 14.0 14134172 13924240 ? Ds Aug29 60:44 postgres:
startup process recovering 00000002000040A3000000B4
$ gstack 4500
#0 0x00000037d10c63a0 in __read_nocancel () from /lib64/libc.so.6
#1 0x00000000005dc88a in FileRead ()
#2 0x00000000005edcb3 in mdread ()
#3 0x00000000005d9160 in ReadBuffer_common ()
#4 0x00000000005d9854 in ReadBufferWithoutRelcache ()
#5 0x000000000048b46c in XLogReadBufferExtended ()
#6 0x00000000004776cb in btree_redo ()
#7 0x0000000000487fe0 in StartupXLOG ()
#8 0x000000000048a0a8 in StartupProcessMain ()
#9 0x000000000049fec3 in AuxiliaryProcessMain ()
#10 0x00000000005c21e6 in StartChildProcess ()
#11 0x00000000005c44e7 in PostmasterMain ()
#12 0x000000000056e8de in main ()
postgres=# select now(),pg_last_xlog_replay_location();
now | pg_last_xlog_replay_location
-------------------------------+------------------------------
2012-08-30 14:34:10.700851+00 | 40A3/B4D62038
postgres=# select now(),pg_last_xlog_replay_location();
now | pg_last_xlog_replay_location
------------------------------+------------------------------
2012-08-30 14:36:49.67801+00 | 40A3/B4D62038
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/hot-standby-lagging-vs-warm-that-is-up-to-date-tp5721711p5721906.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
