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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Thom Brown <thombrown(at)gmail(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:31:07
Message-ID: 4BD870DB.5020908@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-04-28 17:35:35 pgsql: pg_controldata needs #define FRONTEND, same as pg_resetxlog.
Previous Message Tom Lane 2010-04-28 16:54:16 pgsql: Modify ShmemInitStruct and ShmemInitHash to throw errors