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

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Дата
Msg-id 20201123221030.GA12311@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2020-Nov-23, Tom Lane wrote:

> 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.

Looking at that now ...



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

Предыдущее
От: Anastasia Lubennikova
Дата:
Сообщение: Re: New default role- 'pg_read_all_data'
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: PATCH: Batch/pipelining support for libpq