Re: Renaming of pg_xlog and pg_clog
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael.paquier@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-08-26T15:58:45Z
Lists: pgsql-hackers
On Aug 26, 2016 5:54 PM, "Peter Eisentraut" < peter.eisentraut@2ndquadrant.com> wrote: > > On 8/25/16 10:39 PM, Michael Paquier wrote: > > I am relaunching $subject as 10 development will begin soon. As far as > > I know, there is agreement that we can do something here. Among the > > different proposals I have found: > > - pg_clog renamed to pg_commit_status, pg_xact or pg_commit > > - pg_xlog renamed to pg_xjournal, pg_wal or pg_journal > > If we're going to do some renaming, then I suggest we do a > mini-file-system structure under $PGDATA, like > > $PGDATA/etc > $PGDATA/log > $PGDATA/run (lock files etc.) > $PGDATA/tmp > $PGDATA/var > > The names of all the things under "var" could still be refined, but it's > much less likely that users will confuse data with configuration or > plain logs under that scheme Interesting idea. I worry a bit that this might encourage distributions to split it up into different places though, and I'm not sure we want to encourage that.. /Magnus
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