On 5/12/17 12:12, Dagfinn Ilmari Mannsåker wrote:
> Peter Eisentraut 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/fu
On 5/11/17 12:00, Tom Lane wrote:
> Peter Eisentraut 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 wil
Peter Eisentraut 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
On 5/3/17 09:10, David Steele wrote:
> The documentation changes look good to me, but the error message changes
> are a random mix of "WAL" and "write-ahead log", even when referring to
> the same thing.
The reason for this is that some of the error messages refer to a
--waldir option or something
Committed, adjusting for some of the suggestions.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http:
Peter Eisentraut 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
David Fetter wrote:
> On Wed, May 03, 2017 at 10:33:32AM -0700, David Fetter wrote:
> > On Wed, May 03, 2017 at 10:57:06AM -0300, Alvaro Herrera wrote:
> > > Peter Eisentraut wrote:
> > > > Most documentation and error messages still uses the term "transaction
> > > > log" to refer to the write-ahe
On Wed, May 03, 2017 at 10:33:32AM -0700, David Fetter wrote:
> On Wed, May 03, 2017 at 10:57:06AM -0300, Alvaro Herrera wrote:
> > Peter Eisentraut wrote:
> > > Most documentation and error messages still uses the term "transaction
> > > log" to refer to the write-ahead log. Here is a patch to re
On Wed, May 03, 2017 at 10:57:06AM -0300, Alvaro Herrera wrote:
> Peter Eisentraut wrote:
> > 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
Peter Eisentraut wrote:
> 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.
+1 for the idea. I suggest grepping for "transaction
On 5/2/17 9:09 PM, Peter Eisentraut wrote:
> 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.
+1 for the idea.
The documentatio
Peter,
* Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote:
> 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.
Haven't
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Developmen
13 matches
Mail list logo
