Re: Proposal : REINDEX xxx VERBOSE

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Proposal : REINDEX xxx VERBOSE
Дата
Msg-id CA+TgmoaKmEDGyG=vt3EF8Hex3inWhsjB_PtTsP9QuNyCKJsrkA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Proposal : REINDEX xxx VERBOSE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Proposal : REINDEX xxx VERBOSE  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Proposal : REINDEX xxx VERBOSE  (Sawada Masahiko <sawada.mshk@gmail.com>)
Список pgsql-hackers
On Wed, May 13, 2015 at 2:10 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Uh, are we really using INFO to log this?  I thought that was a
> discouraged level to use anymore.  Why not NOTICE?

Well, as Masahiko-san points out, VACUUM uses INFO.  I can't see any
good reason to make this different.

> Also, when multiple tables are reindexed, do we emit lines for each
> index, or only for each table?  If we're going to emit a line for each
> index in the single-table mode, it seems more sensible to do the same
> for the multi-table forms also.

Hmm, yeah, I agree with that.  I thought the patch worked that way,
but I see now that it doesn't.  I think that should be changed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: PATCH: pgbench allow '=' in \set