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

From Michael Paquier
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id CAB7nPqQwU5xTvavOVg3FLrLc3E3URrjH10ccaTkSkjcfy4o=Nw@mail.gmail.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Sat, Oct 22, 2016 at 4:29 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> David Steele wrote:
>> On 10/21/16 3:12 AM, David G. Johnston wrote:
>>
>> > I have no problem continuing keeping with historical precedent and
>> > allowing mnemonic abbreviations in our directory and file names at this
>> > point.
>>
>> I'm still in favor of pg_xact.  A search of the 9.6 docs brings up a number
>> of hits for "xact": pg_last_xact_replay_timestamp(),
>> pg_advisory_xact_lock(), pg_advisory_xact_lock_shared(),
>> pg_last_committed_xact(),  pg_prepared_xacts(), etc. There are also numerous
>> column names that have "xact" in them.
>
> I'm +1 on pg_clog -> pg_xact.

So let's say that's the winner then.

> Also +1 to renaming pg_subtrans to pg_subxact.

Nice suggestion, good naming for consistency with the rest.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: FSM corruption leading to errors
Next
From: Alvaro Herrera
Date:
Subject: Re: emergency outage requiring database restart