Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess
Date
Msg-id CA+TgmobFJLeeypCLWev5ED_dA=oB9QL7uPVQ9xU=GdL__3My2Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On Tue, Feb 14, 2017 at 8:15 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>> I believe that what was agreed was to eliminate "xlog" from
>> user-facing parts of the system, not internal details. [...]
> Ok, I get it. So xlog stays xlog if it is hidden from the user, eg file
> names and probably unexposed functions names, structures or whatever, but
> everything else has been renamed. Fine.

Yeah, generally we didn't rename source files, functions, structures,
or anything like that.  It's still assumed that, if you are developing
core or extension code against PostgreSQL, you know that "xlog" means
"WAL".  But hopefully users won't have to know that any more, once we
get past the inevitable migration pain caused by the changes in v10.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] removing tsearch2
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Sum aggregate calculation for single precsion real