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 20201123224145.GA1405@alvherre.pgsql
обсуждение исходный текст
Ответ на 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
On 2020-Nov-23, Alvaro Herrera wrote:

> On 2020-Nov-23, Tom Lane wrote:
> 
> > Here's a draft patch.
> 
> Here's another of my own.  Outside of elog.c it seems identical.

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.




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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: 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)