Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: pgsql: Introduce wal_level GUC to explicitly control if information
Date
Msg-id 303.1272476307@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-committers
Tree view 
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Thom Brown wrote:
>> 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.

... including in some pre-existing places in the same file.  I think it's
okay as-is.

            regards, tom lane

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: pg_controldata needs #define FRONTEND, same as pg_resetxlog.
Next
From: Thom Brown
Date:
Subject: Re: pgsql: Introduce wal_level GUC to explicitly control if information