Re: [HACKERS] pg_ctl kill support for KILL signal was Re:[COMMITTERS] pgsql: Add test for postmaster crash restarts.
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] pg_ctl kill support for KILL signal was Re:[COMMITTERS] pgsql: Add test for postmaster crash restarts. |
Дата | |
Msg-id | 20171001204854.ph3l6qo7b55yred3@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: [HACKERS] pg_ctl kill support for KILL signal was Re: [COMMITTERS] pgsql: Add test for postmaster crash restarts. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] pg_ctl kill support for KILL signal was Re:[COMMITTERS] pgsql: Add test for postmaster crash restarts.
|
Список | pgsql-hackers |
On 2017-10-01 16:42:44 -0400, Tom Lane wrote: > Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > > On 09/30/2017 10:32 PM, Andres Freund wrote: > >> Heh. I'm inclined to take it out. We could add a --use-the-force-luke > >> type parameter, but it doesn't seem worth it. > > > I agree, but I think we need this discussed on -hackers. Does anyone > > have an objection to allowing "pg_ctl kill KILL somepid"? As Andres > > points out, in most places you can just call kill from the command line > > anyway, so disallowing it is not really a security feature. Having it > > would let us have portable crash restart tests. > > +1 for portable tests, but it still seems like something we don't want > to encourage users to use. What do you think of leaving it out of the > documentation? As far as I can tell we've not documented the set of acceptable signals anywhere but the source. I think we can just keep it that way? Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: