On 30 May 2013 17:43, <federico(at)brandwatch(dot)com> wrote:
> It seems on very large tables the concurrent update with vacuum (or
> autovacuum),
> when the slave is in hot standby mode, generates long loops in read on a
> single wal segment during the recovery process.
Not all aspects of hot standby are optimally tuned, as yet. Some room
for improvement exists.
In some cases, conscious choices were made to keep processing on
master fast at the expense of speed on the standby.
There doesn't seem to be anything which is in itself an error here.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services