Re: [COMMITTERS] pgsql: Remove all references to "xlog" from SQL-callable functions in p

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Remove all references to "xlog" from SQL-callable functions in p
Date: 2017-02-13 17:31:53
Message-ID: CAHGQGwHmRVLfp9U5zk0z8K4Q5t=6X9=6=kf2qgN8hpMuq3=RWg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Feb 14, 2017 at 2:06 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Feb 13, 2017 at 11:43 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> On Fri, Feb 10, 2017 at 5:36 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
>>> Remove all references to "xlog" from SQL-callable functions in pg_proc.
>>>
>>> Commit f82ec32ac30ae7e3ec7c84067192535b2ff8ec0e renamed the pg_xlog
>>> directory to pg_wal. To make things consistent, and because "xlog" is
>>> terrible terminology for either "transaction log" or "write-ahead log"
>>> rename all SQL-callable functions that contain "xlog" in the name to
>>> instead contain "wal". (Note that this may pose an upgrade hazard for
>>> some users.)
>>
>> There are still some mentions to "xlog" in the doc. Maybe we should replace
>> them with "wal" as the attached patch does.
>
> +1. Patch looks good to me.

Thanks! Pushed.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2017-02-13 22:00:25 Re: Re: [COMMITTERS] pgsql: Remove all references to "xlog" from SQL-callable functions in p
Previous Message Fujii Masao 2017-02-13 17:31:24 pgsql: Replace references to "xlog" with "wal" in docs.

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2017-02-13 17:47:45 Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)
Previous Message Robert Haas 2017-02-13 17:14:20 Re: COPY IN/BOTH vs. extended query mode