Re: pg_regress starting postmaster - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_regress starting postmaster
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0FBDD@algol.sollentuna.se
Whole thread Raw
In response to Re: pg_regress starting postmaster  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_regress starting postmaster  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> >> No.  We're a very long way away from considering removing the
> >> postmaster symlink, so it doesn't matter.
>
> > Well, per previous discussion, we're removing
> postmaster.exe from the
> > win32 installer, because it bloats the distribution wihtout
> any gain
> > (remember - windows doesn't have symlinks, so we need a
> complete copy
> > of a file that's 4Mb or so). So it would matter there.
>
> Well, you could copy postgres.exe to postmaster.exe during
> install, so I don't think you ever did need to bloat the
> distribution, only the install footprint.

Except you're not supposed to do that, because the MSI auto-healing and
things like that won't work...

> The question here
> is whether you're ready to break existing custom scripts for
> starting the postmaster.  Maybe there are none such in the
> wild on Windows, but I'd be hesitant to assume that.

We're guessing there aren't - if there are, those are scripts calling
the SCM which in turns starts postgresql. So we're doing it now - if it
turns up in beta that people were actually using it from elsewhere,
we'll jus thave to put it back.

//Magnus


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_regress starting postmaster
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] Bad bug in fopen() wrapper code