Re: Renaming of pg_xlog and pg_clog - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 20160826025539.GA23997@momjian.us
Whole thread Raw
In response to Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Fujii Masao <masao.fujii@gmail.com>)
Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Fri, Aug 26, 2016 at 11:39:29AM +0900, Michael Paquier wrote:
> Now, one of the things discussed as well was that we may want to still
> keep pg_xlog, and soft-link to pg_journal or whatever-the-new-name is
> to not break the existing tools. Personally, I'd prefer a hard break.
> That would not be complicated to fix for any tool maintainers.

I agree on a hard break, unless we get pushback from users, and even
then, they can create the symlinks themselves.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+                     Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [bug fix] Cascading standby cannot catch up and get stuck emitting the same message repeatedly
Next
From: Amit Kapila
Date:
Subject: Re: Why is a newly created index contains the invalid LSN?