| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_ctl kill support for KILL signal was Re: [COMMITTERS] pgsql: Add test for postmaster crash restarts. |
| Date: | 2017-10-01 20:42:44 |
| Message-ID: | 26945.1506890564@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-10-01 20:48:54 | Re: pg_ctl kill support for KILL signal was Re: [COMMITTERS] pgsql: Add test for postmaster crash restarts. |
| Previous Message | Andrew Dunstan | 2017-10-01 20:32:24 | Re: pgsql: Add test for postmaster crash restarts. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-10-01 20:48:54 | Re: pg_ctl kill support for KILL signal was Re: [COMMITTERS] pgsql: Add test for postmaster crash restarts. |
| Previous Message | Andrew Dunstan | 2017-10-01 20:32:24 | Re: pgsql: Add test for postmaster crash restarts. |