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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Дата
Msg-id 20201119033918.GF26172@paquier.xyz
обсуждение исходный текст
Ответ на Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait)
Список pgsql-hackers
Дерево обсуждения 
On Thu, Nov 19, 2020 at 12:13:44PM +0900, Michael Paquier wrote:
> That still looks useful for debugging, so DEBUG1 sounds fine to me.

By the way, it strikes me that you could just do nothing as long as
(log_min_messages > DEBUG1), so you could encapsulate most of the
logic that plays with the lock tag using that.
--
Michael
Вложения

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Move OpenSSL random under USE_OPENSSL_RANDOM
Следующее
От: "tsunakawa.takay@fujitsu.com"
Дата:
Сообщение: RE: Disable WAL logging to speed up data loading