Re: pg_xlog error on the master

From: Venkata B Nagothi <nag1010(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(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 18:22:48
Message-ID: CAEyp7J_ToPhUhLgC5sdcgFXBzGNnFTjQaU4YYvvue_s+j7RDtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sunday, 23 October 2016, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:

> 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?

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

Thanks,
Venkata B N

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Joseph Krogh 2016-10-23 18:37:30 Re: Exclude pg_largeobject form pg_dump
Previous Message Tom Lane 2016-10-23 17:47:56 Assertion failures due to testing visibility without buffer lock