From: Andrew Krause <andrew.krause@breakthroughfuel.com>
To: John Scalia <jayknowsunix@gmail.com>
CC: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Wal archive way behind in streaming replication
Thread-Topic: [ADMIN] Wal archive way behind in streaming replication
Thread-Index: AQHPj91jY83Sv4VgpU+CELm9Snp4MA==
Date: Tue, 24 Jun 2014 18:52:03 +0000
Message-ID: <3709F6AF-032E-4095-B0CB-DC1CE36F6B4B@breakthroughfuel.com>
References: <53A9B567.5070301@gmail.com> <53A9C139.2040704@gmail.com>
In-Reply-To: <53A9C139.2040704@gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <1C97CCF7CADE4E449EA43D2CDCB16EB4@breakthroughfuel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

You shouldn=92t have to touch the files as long as they aren=92t compressed=
.  You may have to restart the standby instance to get the recovery to begi=
n though.  I=92d suggest tailing your instance log and restarting the stand=
by instance.  It should show that the logs from the gap are applying right =
away at startup.=20


Andrew Krause


On Jun 24, 2014, at 1:19 PM, John Scalia <jayknowsunix@gmail.com> wrote:

>=20
> Ok, I did the copy from pg_xlog directory into the restore.conf specified=
directory. The standby servers seem fine with that, however, just copying d=
oes not inform the primary that
> the copy has happened. The archive_status directory under pg_xlog on the =
primary still thinks the last WAL sent was *B7 and yet it's now writing *C9=
. When I did the copy it was
> only up to *C7 and nothing else has shown in the standby's directory.
>=20
> Now, the *.done files in archive_status are just zero length, but I'm a b=
it hesitant to just do a touch for the ones I manually copied as I don't kn=
ow if this is from an in-memory
> queue or if it Postgresql reads the contents of this regularly in order t=
o decide what to copy.
>=20
> Is that safe to do?
>=20
> On 6/24/2014 9:56 AM, Andrew Krause wrote:
>> You can copy all of the WAL logs from your gap to the standby.  If you p=
lace them in the correct location (directory designated for restore) theins=
tance will automatically apply them all.
>>=20
>>=20
>> Andrew Krause
>>=20
>>=20
>>=20
>> On Jun 23, 2014, at 9:24 AM, John Scalia <jayknowsunix@gmail.com> wrote:
>>=20
>>> Came in this morning to numerous complaints from pgpool about the stand=
by servers being behind from the primary. Looking into it, no WAL files had=
 been transferred since late Friday. All I did was restart the primaryand t=
he WAL archving resumed, however, looking at the WAL files on the standby s=
ervers, this is never going to catch up. Now, I've got the archive_timeout =
on the primary =3D 600 or 10 minutes and I see WAL files in pg_xlog every 1=
0 minutes. As they show up on the standby servers, they're also 10 minutes =
apart, but the primary is writing *21 and the standby's areonly up to *10. =
Now, like I said prior, with there being 10 minutes (600seconds) between tr=
ansfers (the same pace as the WALs are generated) it will never catch up. I=
s this really the intended behavior? How would I get the additional WAL fil=
es over to the standbys without waiting 10 minutes to copy them one at a ti=
me?
>>> --
>>> Jay
>>>=20
>>>=20
>>> --
>>> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-admin
>>=20
>=20
>=20
>=20
>=20
>=20
>=20
> --=20
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin