pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replaying 48 WAL files takes 80 minutes
Date: Mon, 29 Oct 2012 11:29:01 -0300
Message-ID: <20121029142901.GE12961@alvh.no-ip.org> (raw)
In-Reply-To: <D960CB61B694CF459DCFB4B0128514C2089A5F80@exadv11.host.magwien.gv.at>
References: <D960CB61B694CF459DCFB4B0128514C2089A5F80@exadv11.host.magwien.gv.at>

Albe Laurenz wrote:
> I am configuring streaming replication with hot standby
> with PostgreSQL 9.1.3 on RHEL 6 (kernel 2.6.32-220.el6.x86_64).
> PostgreSQL was compiled from source.
> 
> It works fine, except that starting the standby took for ever:
> it took the system more than 80 minutes to replay 48 WAL files
> and connect to the primary.
> 
> Can anybody think of an explanation why it takes that long?

Can you do a quick xlogdump of those files?  Maybe there is something
unusual (say particular types of GIN/GiST index updates) on the files
that take longer.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services




view thread (13+ messages)  latest in thread

Message-ID: <20121029142901.GE12961@alvh.no-ip.org>
Permalink:  ../20121029142901.GE12961@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20121029142901.GE12961@alvh.no-ip.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: alvherre@2ndquadrant.com, laurenz.albe@wien.gv.at
  Subject: Re: Replaying 48 WAL files takes 80 minutes
  In-Reply-To: <20121029142901.GE12961@alvh.no-ip.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox