> I don't understand why the change should be "more secure",
> but I see that nobody took care about the possible
> consequences for installation scripts, third party
> applications and so on. :-(((
If the installation scripts and third party apps followed the standard
way of doing it, they wou
I don't understand why the change should be "more secure", but I see
that nobody took care about the possible consequences for installation
scripts, third party applications and so on. :-(((
If you change such essential behaviour (the old behaviour of the
commandline tools did work well since 8.0!
> The latest version (V8.1.4) breaks the setup process of our
> application's installation wizard. We used to call
> "createdb.exe" and piped the password for the postgres user
> (which has been entered by the user in our setup wizard's
> dialogs) into it.
>
> With version V8.1.4 this is not p
The latest version (V8.1.4) breaks the setup process of our
application's installation wizard. We used to call "createdb.exe" and
piped the password for the postgres user (which has been entered by the
user in our setup wizard's dialogs) into it.
With version V8.1.4 this is not possible anymore, t
