Re: [HACKERS] renaming "transaction log" - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] renaming "transaction log"
Date
Msg-id e787c419-cb34-98e6-314f-fb98a4723b3e@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] renaming "transaction log"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5/11/17 12:00, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> Most documentation and error messages still uses the term "transaction
>> log" to refer to the write-ahead log.  Here is a patch to rename that,
>> which I think should be done, to match the xlog -> wal renaming in APIs.
> 
> This will need to be rebased over d10c626de, which made a few of the
> same/similar changes but did not try to hit stuff that wasn't adjacent
> to what it was changing anyway.  I'm +1 for the idea though.  I think
> we should also try to standardize on the terminology "WAL location"
> for LSNs, not variants such as "WAL position" or "log position".

done

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Cached plans and statement generalization
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] renaming "transaction log"