From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: renaming "transaction log" |
Date: | 2017-05-03 17:35:29 |
Message-ID: | 20170503173529.GO14241@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 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$" too -- there are
> > a few cases in SGML that have the phrase "transaction log" split across
> > lines.
>
> In general, you can use ag a.k.a. "The Silver Searcher" for phrase
> searches as follows:
>
> ag $(echo "the phrase to be searched" | sed -e 's/ /\\s/g')
Oops. That should read:
ag $(echo "the phrase to be searched" | sed -e 's/ /\\s+/g')
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Philippe BEAUDOIN | 2017-05-03 17:36:58 | Re: Column rename in an extension update script |
Previous Message | Heikki Linnakangas | 2017-05-03 17:34:21 | Re: password_encryption, default and 'plain' support |