On Wed, Feb 15, 2017 at 8:46 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Now that we've renamed "xlog" to "wal" in user-facing elements, I think
> we should strive to use the name "wal" internally too in new code, not
> "xlog" anymore. This patch introduces several variables, macros,
> functions that ought to change names now -- XLogSegmentOffset should be
> WALSegmentOffset for example. (I expect that as we touch code over
> time, the use of "xlog" will decrease, though not fully disappear).
Ugh.
I think that's going to lead to a complete mess. We'll end up with
newer and older sections of the code being randomly inconsistent with
each other.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company