From: | Lonni J Friedman <netllama(at)gmail(dot)com> |
---|---|
To: | AI Rumman <rummandba(at)gmail(dot)com> |
Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: replication behind high lag |
Date: | 2013-03-25 19:40:11 |
Message-ID: | CAP=oouE8Ds_ouxKZ1p-WSSUN_VNWHiwAycpvDN6rq7fCT9t6OA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 25, 2013 at 12:37 PM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
> Hi,
>
> I have two 9.2 databases running with hot_standby replication. Today when I
> was checking, I found that replication has not been working since Mar 1st.
> There was a large database restored in master on that day and I believe
> after that the lag went higher.
>
> SELECT pg_xlog_location_diff(pg_current_xlog_location(), '0/0') AS offset
>
> 431326108320
>
> SELECT pg_xlog_location_diff(pg_last_xlog_receive_location(), '0/0') AS
> receive, pg_xlog_location_diff(pg_last_xlog_replay_location(), '0/0')
> AS replay
>
> receive | replay
> --------------+--------------
> 245987541312 | 245987534032
> (1 row)
>
> I checked the pg_xlog in both the server. In Slave the last xlog file
> -rw------- 1 postgres postgres 16777216 Mar 1 06:02
> 00000001000000390000007F
>
> In Master, the first xlog file is
> -rw------- 1 postgres postgres 16777216 Mar 1 04:45
> 00000001000000390000005E
>
>
> Is there any way I could sync the slave in quick process?
generate a new base backup, and seed the slave with it.
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2013-03-25 19:43:56 | Re: replication behind high lag |
Previous Message | AI Rumman | 2013-03-25 19:37:59 | replication behind high lag |