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

From Magnus Hagander
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id CABUevEwBrsQWPYCXRj9GGP-MOqbk0Ra=YEX24Y6kD86XDAHOGw@mail.gmail.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
<p dir="ltr"><p dir="ltr">On Aug 26, 2016 5:13 PM, "Joshua D. Drake" <<a
href="mailto:jd@commandprompt.com">jd@commandprompt.com</a>>wrote:<br /> ><br /> > On 08/25/2016 07:39 PM,
MichaelPaquier wrote:<br /> >><br /> >> Hi all,<br /> >><br /> >> I am relaunching $subject as
10development will begin soon. As far as<br /> >> I know, there is agreement that we can do something here. Among
the<br/> >> different proposals I have found:<br /> >> - pg_clog renamed to pg_commit_status, pg_xact or
pg_commit<br/> >> - pg_xlog renamed to pg_xjournal, pg_wal or pg_journal<br /> ><br /> ><br /> > I think
theuse of the pg_ prefix is redundant. Just a directory called: wal will do (for example).<br /> ><br /> > In
referenceto pg_xlog specifically, it should be wal. It is the Write Ahead Log, not the Journal (although I recognize
theycan be synonymous). All the documentation talks about Write Ahead Log.<br /> ><br /><p dir="ltr">Yes, let's
avoidinventing a *third* name for it, please. It's already bad enough that we have both wal and xlog. <p
dir="ltr">/Magnus<br /> 

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Tom Lane
Date:
Subject: Re: PG_DIAG_SEVERITY and a possible bug in pq_parse_errornotice()