Re: Renaming of pg_xlog and pg_clog
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Euler Taveira <euler@timbira.com.br>, Devrim Gündüz <devrim@gunduz.org>, Michael Paquier <michael.paquier@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2016-08-26T14:50:33Z
Lists: pgsql-hackers
* Tom Lane (tgl@sss.pgh.pa.us) wrote: > Euler Taveira <euler@timbira.com.br> writes: > > On 26-08-2016 09:25, Devrim Gündüz wrote: > >> ...and we also have "pg_logical", that includes a "log" keyword already... > > > "clog" and "xlog" is almost "log"; "logical" is not. I don't imagine > > people confusing "logical" meaning "log". > > Well, I dunno; people with a weak grasp of English might have an issue > there. But I never liked that directory name anyway; my problem with > it is I read "pg_logical" and think "logical what?". Naming things using > a disconnected adjective is not good, especially one with as many > potential applications as that one has. If we're up for renaming things > under PGDATA, that one is high on my hit list. iirc, pg_logical also has both temporary and non-temporary data in it too. That complicates things for backup utilities that are trying to exclude all temporary files. If we actually move all the temp files into their own directory (or tree), then we're changing what's in pg_logical anyway, so renaming it seems like a good idea. Thanks! Stephen
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