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

From Andres Freund
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 20160830003427.qqntwf4paavm7acz@alap3.anarazel.de
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 2016-08-29 19:27:29 -0500, Jim Nasby wrote:
> On 8/27/16 1:11 PM, Tom Lane wrote:
> > Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > > I'm for renaming too, but I'd go with Peter E's suggestion: move pg_xlog
> > > to something like $PGDATA/var/wal or $PGDATA/srv/wal or something like that.
> > 
> > I think that would make sense if we were to relocate *everything* under
> > PGDATA into some FHS-like subdirectory structure.  But I'm against moving
> > the config files for previously-stated reasons, and I doubt it makes sense
> > to adopt an FHS-like structure only in part.
> 
> What if we left symlinks for the config files? Or perhaps even better,
> provide a tool that will create them for people that actually need
> them.

See the thread around
http://archives.postgresql.org/message-id/20160826104446.n3cif4m7modslkrs%40msg.df7cb.de



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Peter Eisentraut
Date:
Subject: Re: Renaming of pg_xlog and pg_clog