> > > You'll still need to run the postmaster frmo pg_ctl to
> get the "run
> > > as admin" part. The only part that could be moved is the
> Job Object
> > > for management. And you're normally not going to need
> that one when
> > > you're not running as a service. Maybe sometimes, but I
>
Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > You'll still need to run the postmaster frmo pg_ctl to get the "run as
> > admin" part. The only part that could be moved is the Job Object for
> > management. And you're normally not going to need that one when you're
> > not runn
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> You'll still need to run the postmaster frmo pg_ctl to get the "run as
> admin" part. The only part that could be moved is the Job Object for
> management. And you're normally not going to need that one when you're
> not running as a service. Maybe so
You'll still need to run the postmaster frmo pg_ctl to get the "run as
admin" part. The only part that could be moved is the Job Object for
management. And you're normally not going to need that one when you're
not running as a service. Maybe sometimes, but I doubt it's worth it. If
we could solve
Where are we on this patch?
I am thinking it should be in the most logical place, rather than in
pg_ctl. One call isn't a big deal, especially if you can run the
postmaster without using pg_ctl.
---
Magnus Hagander wrote:
> > If the job object code is moved to the postmaster, it'll
> work when not
> > running as a service as well.
>
> I'd just as soon keep all that Windows-specific cruft in pg_ctl.
> So I think the way you've got it set up is fine.
Well, it'd all be localised to the backend/port/win32 directory
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> If the job object code is moved to the postmaster, it'll work when not
> running as a service as well.
I'd just as soon keep all that Windows-specific cruft in pg_ctl.
So I think the way you've got it set up is fine.
regards,
Naturally, just a minute after sending the patch, I realised how it can
be done better ;)
If the job object code is moved to the postmaster, it'll work when not
running as a service as well. And there's no way to break out of the job
object - it's just the other part.
Yes, I'll set up a new patc