Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Introduce wal_level GUC to explicitly control if information

From: Thom Brown <thombrown(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Introduce wal_level GUC to explicitly control if information
Date: 2010-04-28 17:39:20
Message-ID: i2qbddc86151004281039k3e62cedeg67b50e946da0ecef@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committers
On 28 April 2010 18:31, Heikki Linnakangas <
heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:

> Thom Brown wrote:
> > Just a couple, both in the same file:
> >
> > doc/src/sgml/perform.sgml - s/arcive_mode/archive_mode/ and
>
> Thanks!
>
> > s/afterwards/afterward/
>
> Aren't they interchangeable? Searching the web for "afterward
> afterwrads" turns up various discussion forums, and most seem to
> consider them both correct. And we use "afterwards" elsewhere in the docs.
>
>
> Fair enough.  I assumed American English was used throughout documentation,
and they tend to omit the 's', but I agree.

Thom

In response to

pgsql-committers by date

Next:From: Tom LaneDate: 2010-04-28 19:38:49
Subject: pgsql: Minor editorializing on pg_controldata and pg_resetxlog: adjust
Previous:From: Tom LaneDate: 2010-04-28 17:38:27
Subject: Re: pgsql: Introduce wal_level GUC to explicitly control if information

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group