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

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: pgsql: Introduce wal_level GUC to explicitly control if information
Дата
Msg-id 4BD870DB.5020908@enterprisedb.com
обсуждение исходный текст
Ответ на Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Thom Brown <thombrown@gmail.com>)
Ответы Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Introduce wal_level GUC to explicitly control if information  (Thom Brown <thombrown@gmail.com>)
Список 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

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

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Modify ShmemInitStruct and ShmemInitHash to throw errors
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: pg_controldata needs #define FRONTEND, same as pg_resetxlog.