Re: Renaming of pg_xlog and pg_clog
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Christoph Berg <myon@debian.org>, Bruce Momjian <bruce@momjian.us>, Stephen Frost <sfrost@snowman.net>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael.paquier@gmail.com>, Robert Haas <robertmhaas@gmail.com>,
Thomas Munro <thomas.munro@enterprisedb.com>, Craig Ringer <craig.ringer@2ndquadrant.com>,
Jim Nasby <Jim.Nasby@bluetreble.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Andres Freund <andres@anarazel.de>
Date: 2016-10-20T15:11:50Z
Lists: pgsql-hackers
On Wed, Oct 19, 2016 at 7:05 AM, Christoph Berg <myon@debian.org> wrote: > (tl;dr: rename pg_xlog yes, rename pg_resetxlog only if we have a good > alternative.) I'm amused by the idea of a TL;DR in parentheses at the very bottom of the email, but maybe I'm just easily amused. One idea would be to rename pg_resetxlog to pg_resetwal. I think that's actually an improvement. The "x" in "xlog" is not a clear abbreviation for "write-ahead", especially when we also use "x" in other contexts to mean "transaction" - think "xid". Given our current practices, we could justifiably rename pg_clog to pg_xlog -- after all, that's where we log the status of the xacts. Ugh. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Rename "pg_clog" directory to "pg_xact".
- 88e66d193fba 10.0 landed
-
Improve error reporting in pg_upgrade's file copying/linking/rewriting.
- f002ed2b8e45 10.0 cited