From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, David Fetter <david(at)fetter(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Renaming of pg_xlog and pg_clog |
Date: | 2016-10-21 08:50:36 |
Message-ID: | 55d56627-b0f9-2282-fd1e-b0cf247b7566@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Pantelis Theodosiou | 2016-10-21 08:54:51 | Re: Indirect indexes |
Previous Message | Kyotaro HORIGUCHI | 2016-10-21 08:33:21 | Re: Radix tree for character conversion |