Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Introduce wal_level GUC to explicitly control if information - Mailing list pgsql-committers

From Heikki Linnakangas
Subject Re: pgsql: Introduce wal_level GUC to explicitly control if information
Date
Msg-id 4BD870DB.5020908@enterprisedb.com
Whole thread Raw
In response to Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Thom Brown <thombrown@gmail.com>)
Responses Re: pgsql: Introduce wal_level GUC to explicitly control if information
Re: pgsql: Introduce wal_level GUC to explicitly control if information
List pgsql-committers
Tree view 
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

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Modify ShmemInitStruct and ShmemInitHash to throw errors
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: pg_controldata needs #define FRONTEND, same as pg_resetxlog.