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

From Peter Eisentraut
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 78d8090c-84c3-3eb6-0b6a-5a4db90d6fbb@2ndquadrant.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/4/16 1:48 AM, Michael Paquier wrote:
> So this is still open for votes. Here are the candidates and who
> voiced for what:
> - pg_transaction: Michael P, Thomas M. => Current 0002 is doing that.
> - pg_xact: David S, Robert
> - pg_trans: Tom
> - pg_transaction_status: Peter E.

I think this would all be a lot easier if we just moved all the pg_*
directories one directory down.  We did this with "global" many years
ago and it worked out well.  We didn't actually have to change the file
names, the top-level directory became cleaner, and no one was messing
around with the files anymore.  Adjusting external tools also becomes
easier.  There is so much lore out there about clog and xlog; it would
be annoying to break with that.

I can see a reason for not doing that with pg_xlog, because that is a
bit of an external interface, with initdb -X and such, and pg_wal is a
pretty good alternative name.  But no one deals with these other
directories directly, so just move them out of the way.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1
Next
From: Stephen Frost
Date:
Subject: Re: Remove "Source Code" column from \df+ ?