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

From Jim Nasby
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 66896734-c544-f71d-0531-89238cf0b39b@BlueTreble.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
Re: Renaming of pg_xlog and pg_clog  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/14/16 9:06 AM, Stephen Frost wrote:
>> > And internal/base and internal/global and internal/pg_... because
>> > these shouldn't be touched by the users either.
>> >
>> > I don't think this would lead anywhere.
> It'd probably be easier to move the things that are *not* PG internal
> (eg: config files, et al) *out* of the data directory and into somewhere
> sensible, like /etc ...

I do think it would be an improvement to segregate things users are 
expected to touch (*.conf and pg_log are what come to mind) from 
everything else, which could easily be done by moving everything else to 
an internal/ directory. I agree that's not much of an improvement for 
pg_[cx]log, but we could create internal/ as well as rename some things.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.
Next
From: Robert Haas
Date:
Subject: tablesample test failure with small TOAST_TUPLE_THRESHOLD