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

Поиск
Список
Период
Сортировка
Искать
От
Bruce Momjian
Тема
Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p
Дата
в 20:58:49
Msg-id
200405192358.i4JNwAw21161@candle.pha.pa.us
Ответ на
Список
Дерево обсуждения
Re: [COMMITTERS] pgsql-server/src backend/main/main.c b Claudio Natoli <claudio.natoli@memetrics.com>
Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p Bruce Momjian <pgman@candle.pha.pa.us>
Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p Tom Lane <tgl@sss.pgh.pa.us>
Re: [COMMITTERS] pgsql-server/src backend/main/main.c b ackend/p Bruce Momjian <pgman@candle.pha.pa.us>
Tom Lane wrote:
> Bruce Momjian  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
В списке pgsql-patches по дате отправления
От: Bruce Momjian
Дата:
От: Bruce Momjian
Дата:
FAQ