Re: dropdb --force

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: dropdb --force
Дата
Msg-id CAFj8pRBVKb-GNNit-g8n4iZXNZTKfF6ZqHZkOWdb=-xN409CRw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: dropdb --force  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers



I am sending patch where kill was replaced by SendProcSignal. I tested it on pg_bench with 400 connections, and it works without problems.

I tested it under high load and it is works. But it is slower than just kill - under load the killing 400 connections needs about 1.5 sec.

Maybe for forced drop database we can increase max time limit to 10 seconds (maybe more (statement timeout)) ? It is granted so we wait just on sigterm handling. Other situations are finished by error. So in this case is very probable so waiting will be successful and then we can wait long time.


Regards

Pavel

Pavel


--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: CREATE TEXT SEARCH DICTIONARY segfaulting on 9.6+
Следующее
От: Dent John
Дата:
Сообщение: Re: The flinfo->fn_extra question, from me this time.