Re: windows / initdb oddness - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: windows / initdb oddness
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE6C8069@algol.sollentuna.se
Whole thread Raw
In response to windows / initdb oddness  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> >Is there any reason to worry about an accidental environment
> conflict?
> >If someone mistakenly did "export PG_RESTRICT_EXEC=1", it
> looks to me
> >like this would cause the re-exec bit to be skipped, but I
> suppose the
> >worst possible consequence is that the postmaster would
> refuse to start.
> >Is there anything I don't see?  (Of course, the magic
> argument method
> >can be broken manually in just the same way...)
> >
> >
> >
> >
>
> Yes. The effect would be that we just do exactly what we do
> today anyway.  We could make the value some more obscure
> token, but I don't see much point.

No, if the user wants to break it, go ahead. They're just going to break
things for themselves (since the execuited postgres.exe still retains
the admin check and will bail out). I see no reason to make it obscure.

//Magnus


pgsql-hackers by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: windows / initdb oddness
Next
From: "Jim C. Nasby"
Date:
Subject: Divid by zero bug in float