pg_xlog error on the master

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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Sunday, 23 October 2016, Michael Paquier <michael.paquier@gmail.com>
wrote:

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?

Oops. My bad. All works fine now. Sorry for the confusion.

Thanks,
Venkata B N