Re: Renaming of pg_xlog and pg_clog - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 20161014113523.GZ13284@tamriel.snowman.net
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Christoph Berg <myon@debian.org>)
Re: Renaming of pg_xlog and pg_clog  (Magnus Hagander <magnus@hagander.net>)
Re: Renaming of pg_xlog and pg_clog  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
* Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
> On 10/12/16 11:22 AM, Tom Lane wrote:
> > 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.
>
> I think it would help if we moved it to something like
> "internal/pg_xlog" and "internal/pg_clog".  Keep the name but move it
> out of sight.

I disagree that this will materially help with the issue.

> We have a tool called pg_xlogdump in the standard installation.  initdb
> has an option --xlogdir, pg_basebackup has --xlog and others.  Renaming
> the xlog directory would make this all a bit confusing, unless we're
> prepared to rename the programs and options as well.

pg_xlogdump is not a user-facing tool, frankly, so I don't believe we
should be terribly concerned about either leaving it named as-is or
renaming it.  I agree that we should consider adding alternative names
to the options for initdb and pg_basebackup.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: process type escape for log_line_prefix
Next
From: Heikki Linnakangas
Date:
Subject: Re: Password identifiers, protocol aging and SCRAM protocol