From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Joshua Drake <jd(at)commandprompt(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Renaming of pg_xlog and pg_clog |
Date: | 2016-08-26 15:14:36 |
Message-ID: | CABUevEwBrsQWPYCXRj9GGP-MOqbk0Ra=YEX24Y6kD86XDAHOGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Aug 26, 2016 5:13 PM, "Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
>
> On 08/25/2016 07:39 PM, Michael Paquier wrote:
>>
>> Hi all,
>>
>> I am relaunching $subject as 10 development will begin soon. As far as
>> I know, there is agreement that we can do something here. Among the
>> different proposals I have found:
>> - pg_clog renamed to pg_commit_status, pg_xact or pg_commit
>> - pg_xlog renamed to pg_xjournal, pg_wal or pg_journal
>
>
> I think the use of the pg_ prefix is redundant. Just a directory called:
wal will do (for example).
>
> In reference to pg_xlog specifically, it should be wal. It is the Write
Ahead Log, not the Journal (although I recognize they can be synonymous).
All the documentation talks about Write Ahead Log.
>
Yes, let's avoid inventing a *third* name for it, please. It's already bad
enough that we have both wal and xlog.
/Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-08-26 15:26:52 | Re: PG_DIAG_SEVERITY and a possible bug in pq_parse_errornotice() |
Previous Message | Joshua D. Drake | 2016-08-26 15:13:04 | Re: Renaming of pg_xlog and pg_clog |