Re: dropdb --force - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: dropdb --force
Date
Msg-id CAFj8pRBVKb-GNNit-g8n4iZXNZTKfF6ZqHZkOWdb=-xN409CRw@mail.gmail.com
Whole thread Raw
In response to Re: dropdb --force  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: CREATE TEXT SEARCH DICTIONARY segfaulting on 9.6+
Next
From: Dent John
Date:
Subject: Re: The flinfo->fn_extra question, from me this time.