| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Venkata B Nagothi <nag1010(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog error on the master |
| Date: | 2016-10-23 08:33:49 |
| Message-ID: | CAB7nPqQ_d9-JLe-ON96_ON4gnGm4Kk_R9=a4XHNgeLkw5U0irA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 23, 2016 at 5:05 PM, Venkata B Nagothi <nag1010(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-10-23 12:34:07 | Re: Renaming of pg_xlog and pg_clog |
| Previous Message | Vik Fearing | 2016-10-23 08:18:16 | Re: Renaming of pg_xlog and pg_clog |