Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal - Mailing list pgsql-hackers

From Vladimir Rusinov
Subject Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
Date
Msg-id CAE1wr-wNZeSTUpLSh2Qt3Q91-qdpRLmd74u-7t=MuHmdtRNnRQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers

On Fri, Jan 27, 2017 at 11:03 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
1. Rename nothing
2. Rename directory only
3. Rename everything

3 or 1 (with a slight preference for 3).

Not sure if my vote counts, but for me as ex-DBA consistency mattered a lot.
This is one of the reasons PostgreSQL is actually nicer to work with than many other databases. I remember 'wal' vs 'xlog' was actually one of a very few confusing things. I think it is important to stick to just one term, whether it be wal or xlog. I'd prefer wal since it's a term used in many other systems. 'xlog' may be confused with likes of binary log in MySQL which is not what it is.

Now, I've rebased my patches to rename functions (with and without aliases) on top of current master, but there's probably no point of posting them now given there are patches above that rename other things as well.

--
Vladimir Rusinov
Storage SRE, Google Ireland

Google Ireland Ltd.,Gordon House, Barrow Street, Dublin 4, Ireland
Registered in Dublin, Ireland
Registration Number: 368047

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Superowners
Next
From: Etsuro Fujita
Date:
Subject: Re: [HACKERS] Push down more full joins in postgres_fdw