Re: Renaming of pg_xlog and pg_clog
Jim Nasby <jim.nasby@bluetreble.com>
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Stephen Frost <sfrost@snowman.net>, Christoph Berg <myon@debian.org>, 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>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2016-10-14T16:10:49Z
Lists: pgsql-hackers
On 10/14/16 9:06 AM, Stephen Frost wrote: >> > And internal/base and internal/global and internal/pg_... because >> > these shouldn't be touched by the users either. >> > >> > I don't think this would lead anywhere. > It'd probably be easier to move the things that are *not* PG internal > (eg: config files, et al) *out* of the data directory and into somewhere > sensible, like /etc ... I do think it would be an improvement to segregate things users are expected to touch (*.conf and pg_log are what come to mind) from everything else, which could easily be done by moving everything else to an internal/ directory. I agree that's not much of an improvement for pg_[cx]log, but we could create internal/ as well as rename some things. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
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