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 197305.1606171703@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Список pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Your version has the advantage that errstart() doesn't get a new
> function call.  I'm +1 for going with that ... we could avoid the
> duplicate code with some additional contortions but this changes so
> rarely that it's probably not worth the trouble.

I was considering adding that factorization, but marking the function
inline to avoid adding overhead.  Most of elog.c predates our use of
inline, so it wasn't considered when this code was written.

            regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: pg_ls_tmpdir to show directories and shared filesets (and pg_ls_*)