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

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

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: pg_controldata needs #define FRONTEND, same as pg_resetxlog.
Следующее
От: Thom Brown
Дата:
Сообщение: Re: pgsql: Introduce wal_level GUC to explicitly control if information