Re: [COMMITTERS] pgsql: Blind attempt at a Cygwin fix - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Blind attempt at a Cygwin fix
Date
Msg-id 56913CCA.4080509@dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Blind attempt at a Cygwin fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Blind attempt at a Cygwin fix  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers

On 01/08/2016 11:17 AM, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> Alvaro Herrera wrote:
>>> Obviously this wasn't the best idea ever.  Andrew suggests on IM to
>>> revert this on Cygwin to just do the "isatty" check as originally.
>> Here's a proposed patch.  Thoughts?
> Ugly, but it will hold the fort until someone can debug the service
> code for Cygwin.
>
>             


I downloaded the official Cygwin packages into a Cygwin instance and 
checked how they do things. As I rather expected, they do not use pg_ctl 
at all to install or run as a service. Rather, they use the standard 
Cygwin service utility cygrunsrv. This is all managed via a SYSV style 
init script.

So if anything I'd be inclined to disable all the service-related code 
in pg_ctl for Cygwin, and treat it just as we treat Unix.

cheers

andrew



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: checkpointer continuous flushing
Next
From: Artur Zakirov
Date:
Subject: Re: [PROPOSAL] Improvements of Hunspell dictionaries support