Re: BUG #6094: Streaming replication does not catch up when writing enough data

On Thu, Jul 7, 2011 at 1:05 PM, David Hartveld
<david.hartveld@mendix.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A06094
> Logged by: =A0 =A0 =A0 =A0 =A0David Hartveld
> Email address: =A0 =A0 =A0david.hartveld@mendix.com
> PostgreSQL version: 9.1-beta2
> Operating system: =A0 Debian GNU/Linux 6.0.2 "Squeeze"
> Description: =A0 =A0 =A0 =A0Streaming replication does not catch up when =
writing
> enough data
> Details:
>
> After creation of two new clusters, and setting them up as master and sla=
ve
> (in async mode, according to the current 9.1 docs), the execution of a la=
rge
> SQL script (creating a db, tables, sequences, etc., filling them with data
> through COPY) runs properly on the master, but does not stream to the sla=
ve,
> i.e. the slave does not catch up. In the master log, the following line is
> printed many times:

Your output indicates that there is a problem in your replication
setup and this is why the slave does not catch up.

This is not a performance issue. It is either a bug in replication, or
a user configuration issue. Since few things have changed in 9.1 in
this area, at the moment the balance of probablity if user error. If
you can provide a more isolated bug report we may be able to
investigate.

This is being discussed in a thread on the General list and there is
no reason to post twice.

--=20
=A0Simon Riggs=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 http:/=
/www.2ndQuadrant.com/
=A0PostgreSQL Development, 24x7 Support, Training & Services