Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal |
Дата | |
Msg-id | CAB7nPqRtpxrj3EQ+frokP0h-OPtZZ5_rkBfbkYpSQXeNXi8Jvw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal (Vladimir Rusinov <vrusinov@google.com>) |
Список | pgsql-hackers |
On Mon, Jan 30, 2017 at 8:01 PM, Vladimir Rusinov <vrusinov@google.com> wrote: > > 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. Any voice counts :) > 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. The first time I worked on Postgres, I was not able to do the mapping between both terms as well. > 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. OK, I have moved this patch to CF 2017-03, let's make the discussion continue with more votes coming in. -- Michael
В списке pgsql-hackers по дате отправления: