Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Дата
Msg-id 166823.1606168975@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Список pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Well, we already do this in a number of places.  But I can get behind
> this:

>> Maybe it'd be a good idea to have elog.c expose a new function
>> along the lines of "bool message_level_is_interesting(int elevel)"
>> to support this and similar future optimizations in a less fragile way.

I'll see about a patch for that.

            regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: optimizer/clauses.h needn't include access/htup.h
Следующее
От: Anastasia Lubennikova
Дата:
Сообщение: Re: New default role- 'pg_read_all_data'