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

From Fujii Masao
Subject Re: [HACKERS] Renaming of pg_xlog and pg_clog
Date
Msg-id CAHGQGwGUoeFwB313VHOQzvO_CckdmaPxqOUugz9uC1-cQdFqng@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Fri, Mar 17, 2017 at 11:03 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Fri, Mar 17, 2017 at 10:58 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> Fine!  I've committed the pg_clog renaming, but I'd really like to
>> draw the line here.  I'm not going to commit the pg_subtrans ->
>> pg_subxact naming and am -1 on anyone else doing so.  I think that
>> having the names of things in the code match what shows up in the file
>> system is an awfully desirable property which we should preserve
>> insofar as we can do so without compromising other goals.  Not
>> invalidating what users and DBAs think they know about how PostgreSQL
>> works is a good thing, too; there are a lot more people who know
>> something about the directory layout than will read this thread.
>
> I'm cool with that, thanks for the commit.

monitoring.sgml still has some references to "clog". We should update them?

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] New CORRESPONDING clause design
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] New CORRESPONDING clause design