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 of
> course, except for a single call - where there is already "windows
> cruft".
> 
> But. I see your point. And the  vast majority of production
> installations run as service anyway. So I won't spend any time making
> those changes, I'll leave what's on -patches now.
> 
> //Magnus
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

• Re: [PATCHES] Fix for running from admin account on win32 at 2006-01-14 20:18:18 from Magnus Hagander

pgsql-hackers by date

Next:	From: Chris Campbell	Date: 2006-02-03 14:18:51
	Subject: Re: Passing arguments to views
Previous:	From: Bruce Momjian	Date: 2006-02-03 13:51:06
	Subject: Re: [HACKERS] Some platform-specific MemSet research

pgsql-patches by date

Next:	From: Peter Eisentraut	Date: 2006-02-03 15:06:02
	Subject: Re: Multiple logical databases
Previous:	From: Bruce Momjian	Date: 2006-02-03 13:51:06
	Subject: Re: [HACKERS] Some platform-specific MemSet research