From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Ulrich Neumann <U_Neumann(at)gne(dot)de>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Antw: Re: Patch for NetWare support |
Date: | 2002-08-12 22:25:25 |
Message-ID: | 19205.1029191125@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Most likely, we would define a port name in configure.in and test for
> that before accepting that flag. Also, there would be _no_
> documentation of this flags existance in the PostgreSQL documentation.
> It is only used by the postmaster calling postgres, so that should be
> OK.
I concur with Peter: there seems to be no need for this hack at all.
Just install two copies of the postmaster/postgres executable --- ie,
use cp instead of ln on platforms where ln doesn't work. The postgres
executable would only be used for standalone-backend operation, which'd
probably mean you could remove it after initdb, if the disk space hit
bothers you.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Denis A Ustimenko | 2002-08-13 02:54:11 | connect_timeout parameter in libpq |
Previous Message | Stephan Szabo | 2002-08-12 22:22:08 | Re: Fix disabled triggers with deferred constraints |