Re: renaming "transaction log"

From: ilmari(at)ilmari(dot)org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=)
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: renaming "transaction log"
Date: 2017-05-12 16:12:18
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:

> Committed, adjusting for some of the suggestions.

Looks like one occurrence was still left in:

$ ag --no-group --ignore po --ignore release-\* --ignore wal.sgml '\btransaction\s+log\b'
doc/src/sgml/func.sgml:18631: end of the transaction log at any instant, while the write location is the end of

The four other occurrences in the same paragraph were fixed, so I assume
this was just an oversight.

- ilmari
"I use RMS as a guide in the same way that a boat captain would use
a lighthouse. It's good to know where it is, but you generally
don't want to find yourself in the same spot." - Tollef Fog Heen

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitriy Sarafannikov 2017-05-12 16:12:49 Re: [PROPOSAL] Use SnapshotAny in get_actual_variable_range
Previous Message Tom Lane 2017-05-12 16:04:54 Re: eval_const_expresisions and ScalarArrayOpExpr