Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p
Date: 2004-05-19 23:58:10
Message-ID: 200405192358.i4JNwAw21161@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(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

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-05-20 00:42:09 Re: [PORTS] Building PgSQL 7.4.2 on SGI Irix 6.19
Previous Message Bruce Momjian 2004-05-19 23:56:13 Re: [GENERAL] Question about rtrees (overleft replacing left in nodes)