On Sat, Oct 22, 2016 at 07:33:56AM +0900, Michael Paquier wrote: > On Sat, Oct 22, 2016 at 4:29 AM, Alvaro Herrera > <alvhe...@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.
Agreed. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
