Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Claudio Natoli wrote:
> >> There's also the possibility of adding it to read/write_backend_variables,
> >> just as we add other variables for fork/exec that we want the backends to
> >> inherit.
>
> > In the exec case, the executable name is actually different from the
> > postmaster, so passing it doesn't make sense.
>
> How much do we care? AFAIK we only really care about the directory part
> of the path, no? There are ports that need the exact executable
> pathname for dynamic loading purposes, but I'd think Windows is not one
> of them.
Agreed, but I figured we should be accurate if we can. For fork-only,
our binary is postmaster, while for fork/exec, it is postgres.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
