From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | PGSQL-Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | A patch to pg_regress for Windows port |
Date: | 2007-01-05 19:18:47 |
Message-ID: | 65937bea0701051118q5bb41460ke2c2d62b89cb408d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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.
Is this new pg_ctl behavior mentioned anywhere in the docs?
Best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
Attachment | Content-Type | Size |
---|---|---|
pg_regress.c.patch.gz | application/x-gzip | 451 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-05 19:21:19 | COPY with no WAL, in certain circumstances |
Previous Message | David Fetter | 2007-01-05 19:02:13 | Re: -f <output file> option for pg_dumpall |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-05 19:21:19 | COPY with no WAL, in certain circumstances |
Previous Message | Zeugswetter Andreas ADI SD | 2007-01-05 16:25:08 | Re: [HACKERS] wal_checksum = on (default) | off |