Re: replication behind high lag
От | Lonni J Friedman |
---|---|
Тема | Re: replication behind high lag |
Дата | |
Msg-id | CAP=oouE8Ds_ouxKZ1p-WSSUN_VNWHiwAycpvDN6rq7fCT9t6OA@mail.gmail.com обсуждение исходный текст |
Ответ на | replication behind high lag (AI Rumman <rummandba@gmail.com>) |
Ответы |
Re: replication behind high lag
|
Список | pgsql-general |
On Mon, Mar 25, 2013 at 12:37 PM, AI Rumman <rummandba@gmail.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.
В списке pgsql-general по дате отправления: