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

From David Steele
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 55d56627-b0f9-2282-fd1e-b0cf247b7566@pgmasters.net
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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.

It's not just an arcane developer term when it shows up in a number of 
our user-facing functions/columns.

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Radix tree for character conversion
Next
From: Pantelis Theodosiou
Date:
Subject: Re: Indirect indexes