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

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: pgsql: Introduce wal_level GUC to explicitly control if information
Дата
Msg-id i2qbddc86151004281039k3e62cedeg67b50e946da0ecef@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-committers
Дерево обсуждения
On 28 April 2010 18:31, Heikki Linnakangas <heikki.linnakangas@enterprisedb.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

В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Introduce wal_level GUC to explicitly control if information
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Minor editorializing on pg_controldata and pg_resetxlog: adjust