Re: Log archiving failing. Seems to be wrong timeline
| От | Chris Lewis |
|---|---|
| Тема | Re: Log archiving failing. Seems to be wrong timeline |
| Дата | |
| Msg-id | 5776403E.2080907@inview.co.uk обсуждение исходный текст |
| Ответ на | Re: Log archiving failing. Seems to be wrong timeline (Jeff Janes <jeff.janes@gmail.com>) |
| Список | pgsql-general |
Hi Jeff, Done as you advised and now things are working again. Many thanks Chris On 30/06/16 20:19, Jeff Janes wrote: > On Thu, Jun 30, 2016 at 3:53 AM, Chris Lewis <clewis@inview.co.uk> wrote: >> Hello, >> >> We have 2 postgresql servers (v 9.4.2) master and slave in streaming >> replication. The overall cluster is controlled using pacemaker & corosync >> and the pgsql cluster agent which handles failover to, and promotion of, the >> slave. >> >> Recently a failover occured and I noticed that log archiving was failing on >> the master: > ... > >> Why are we trying to archive logs which belong to an old timeline? > Just because the timeline is old doesn't mean we want to destroy it. > Afterall, the reason for having timelines in the first place is to > preserve, not to destroy. > > It sounds like someone removed the old timeline's log files from > pg_xlog, but did not remove the corresponding .ready files from > pg_xlog/archive_status. > > If the old timeline's files are truly lost, then you will have to > carefully remove those corresponding .ready files. > > Cheers, > > Jeff -- Chris Lewis Systems Administrator Inview Technology Ltd. T: +44 (0) 1606 812500 M: +44 (0) 7980 446907
В списке pgsql-general по дате отправления: