Re: Renaming of pg_xlog and pg_clog
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: 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-12T15:22:06Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > On 10/4/16 1:48 AM, Michael Paquier wrote: >> So this is still open for votes. Here are the candidates and who >> voiced for what: >> - pg_transaction: Michael P, Thomas M. => Current 0002 is doing that. >> - pg_xact: David S, Robert >> - pg_trans: Tom >> - pg_transaction_status: Peter E. > I think this would all be a lot easier if we just moved all the pg_* > directories one directory down. The main problem we're trying to fix here is people thinking that something with "log" in the name contains discardable data. Just relocating the directory without renaming it won't improve that. The relocation aspect was meant to address another problem, which is making it easier to distinguish which parts of the tree should be copied by tools like pg_basebackup. But that's not what Michael is asking for votes on. regards, tom lane
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