it is still stuck on the same wal record ->
now | pg_last_xlog_replay_location
---+--
2012-08-30 14:57:57.617171+00 | 40A3/B4D62038
and iostat shows 100% util on one disk ->
sdj 90.60 0.00 176.0
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 000240A300B4
$ gstack 4500
#0 0x0037d10c63a0 in __read_nocancel () from /lib64/libc.so.6
#1 0x005dc88a i
MirrorX writes:
> i am facing a rather 'weird' issue so please if you have ideas/thoughs share
> them.
> i have a setup of a master server and hot standby one. the database settings
> on both are identical, the specs of the servers are the same except of the
> disks. the disks on the standby are
hello!
i am facing a rather 'weird' issue so please if you have ideas/thoughs share
them.
i have a setup of a master server and hot standby one. the database settings
on both are identical, the specs of the servers are the same except of the
disks. the disks on the standby are much slower than th
