On Wed, Jun 13, 2012 at 04:08:20PM +0100, Dave Page wrote:
> On Wed, Jun 13, 2012 at 3:51 PM, Bruce Momjian <br...@momjian.us> wrote:
> > On Mon, Jun 11, 2012 at 10:23:00PM -0400, Tom Lane wrote:
> >> Hm, that patch seems to be several bricks shy of a load. I will fix
> >> two obvious bugs in it:
> >>
> >> (1) not dump core on boxes where printf("%s", NULL) dumps core;
> >>
> >> (2) not try to call adjust_data_dir before complaining for lack of
> >> a -D switch; since adjust_data_dir does not do anything to the value
> >> of pg_config, it's just silly to do things in that order.
> >>
> >> However,
> >>
> >> > I note that "postgres -C data_directory" will refuse to run on the
> >> > command line because I've got admin privileges in Windows, and that
> >> > pg_ctl normally starts postgres.exe using CreateRestrictedProcess.
> >> > But it does not do so for the popen call in adjust_data_dir.
> >>
> >> if that actually is a third bug, as seems likely, somebody with access
> >> to a windows environment will need to deal with it.
> >
> > I think you have to use RUNAS when using 'pg_ctl' or 'postgres' on Windows.
>
> pg_ctl should work as an administrative user, as it'll irrevocably
> drop unwanted privileges. postgres won't though.
The user was geting an error trying to start the postmaster, which I
think matches your description.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
