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

From Joshua D. Drake
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id f1261e6b-2903-405e-3575-2e667f194a8d@commandprompt.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Renaming of pg_xlog and pg_clog  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 08/27/2016 11:11 AM, 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.

I think that is a very reasonable suggestion.

Also as a note to the idea that we make break things for external user 
space; the next version being v10 is the exact time to do that.

JD

>
>             regards, tom lane
>
>


-- 
Command Prompt, Inc.                  http://the.postgres.company/                        +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Missing checks when malloc returns NULL...
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Renaming of pg_xlog and pg_clog