Re: pg_xlog error on the master - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_xlog error on the master
Date
Msg-id CAB7nPqQ_d9-JLe-ON96_ON4gnGm4Kk_R9=a4XHNgeLkw5U0irA@mail.gmail.com
Whole thread Raw
In response to pg_xlog error on the master  (Venkata B Nagothi <nag1010@gmail.com>)
Responses Re: pg_xlog error on the master  (Venkata B Nagothi <nag1010@gmail.com>)
List pgsql-hackers
On Sun, Oct 23, 2016 at 5:05 PM, Venkata B Nagothi <nag1010@gmail.com> wrote:
> I just did did a "git pull" to test one of my patches and i get the
> following error :
>
> 2016-10-23 18:51:47.679 AEDT [31930] FATAL:  could not open archive status
> directory "pg_xlog/archive_status": No such file or directory
> 2016-10-23 18:51:47.679 AEDT [31841] LOG:  archiver process (PID 31930)
> exited with exit code 1
>
> is it expected ?

No.

> I notice that pg_xlog's name has been changed to pg_wal. I am not sure about
> this.

WAL archiving works correctly here, and tests in src/test/recovery/
work. Are you sure that you cleaned up up your source tree before
recompiling?
-- 
Michael



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Michael Paquier
Date:
Subject: Re: Renaming of pg_xlog and pg_clog