| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: renaming "transaction log" |
| Date: | 2017-05-12 17:52:52 |
| Message-ID: | e787c419-cb34-98e6-314f-fb98a4723b3e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/11/17 12:00, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-05-12 17:54:08 | Re: renaming "transaction log" |
| Previous Message | Bruce Momjian | 2017-05-12 17:43:44 | Re: Cached plans and statement generalization |