| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Re: MSVC odd TAP test problem |
| Date: | 2017-05-10 23:07:43 |
| Message-ID: | CAB7nPqSVDzynozxALXk9r80rVvH3Erk9Hxx_wUJ+DahnDFaVyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 11, 2017 at 7:29 AM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> This isn't going to work. If you look at the code in IPC/Run.pm you see
> that the coup_d_grace signal is only used after it has first sent the
> hardcoded SIGTERM. It might be tempting to play with using Sysinternals'
> pskill utility, but we can hardly expect buildfarm owners and others to
> hack their copies of IPC/Run.pm, so I'm going to go ahead and commit the
> changes I proposed.
OK, thanks for checking. That was worth a try.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2017-05-11 00:15:17 | Re: Should pg_current_wal_location() become pg_current_wal_lsn() |
| Previous Message | Andrew Dunstan | 2017-05-10 22:29:56 | Re: Fwd: Re: MSVC odd TAP test problem |