Re: A patch to pg_regress for Windows port - Mailing list pgsql-patches

From Gurjeet Singh
Subject Re: A patch to pg_regress for Windows port
Date
Msg-id 65937bea0701051157t7414cffp5cacec63867160a3@mail.gmail.com
Whole thread Raw
In response to Re: A patch to pg_regress for Windows port  (Magnus Hagander <magnus@hagander.net>)
List pgsql-patches
cool...

On 1/6/07, Magnus Hagander <magnus@hagander.net> wrote:
Gurjeet Singh wrote:
> On Windows, if logged in as an Administrator, 'make check' fails with
> our standard error, saying:
>
> <quote>
> Execution of PostgreSQL by a user with administrative permissions is not
> permitted.
> The server must be started under an unprivileged user ID to prevent
> possible system security compromises.  See the documentation for
> more information on how to properly start the server.
> </quote>
>
> But, for some time now, a Windows' Administrator *can* run a postgres
> without having to create a normal user; he just has to use pg_ctl to do
> so. Thanks to code written by Magnus, pg_ctl gives up it's
> administrative privilges before starting the postmaster, and hence the
> postmaster runs without critical privileges.
>
> So I thought that 'make check' could also make use of that
> functionality, and hence this patch.

Per previous discussion with Tom (in the archives, but I can't get there
right now), this is the wrong way to do it. We lose the ability to kill
the postmaster if it fails.

I have a proper working solution in my tree that I will submit soon
along with the changes required to make pg_regress work in a non-msys
environment using MSVC.

//Magnus




--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet @{ gmail | hotmail | yahoo }.com

pgsql-patches by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: A patch to pg_regress for Windows port
Next
From:
Date:
Subject: Re: Updated XML patch