Tom Lane wrote:
[useful an complete discussion of sbin-style programs and their place
snipped]
> (Not sure about pg_dump/pg_dumpall/pg_restore; are these of any
> significant use to non-superusers?) This would keep createuser/dropuser
> out of the shared bin directory, which certainly seem like
"Oliver Elphick" <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> I think it would be a real bad idea to put the postmaster and postgres
>>> executables right in /usr/local/bin. Perhaps it is time to think about
>>> a separate 'sbin' directory for programs that aren't supposed to be
>>> invoked
Lamar Owen wrote:
>Tom Lane wrote:
>> To do that without creating problems, we'd have to go back to making
>> sure that all the programs we install have 'pg'-prefixed names. The
>> scripts (createdb and so forth) don't at the moment, and names like
>> 'createuser' clearly have potential
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > My proposal is to set includedir=${prefix}/include/postgresql (instead of
> > ${prefix}/include) in such cases where the prefix is shared, i.e., it does
> > not contain something like "pgsql" already. (precise pattern t.b.d.)
> H
On Wed, Sep 27, 2000 at 10:53:43AM -0400, Tom Lane wrote:
> I think it would be a real bad idea to put the postmaster and postgres
> executables right in /usr/local/bin. Perhaps it is time to think about
> a separate 'sbin' directory for programs that aren't supposed to be
> invoked by normal use
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> It would be desirable for several reasons that PostgreSQL can be installed
> safely with --prefix=/usr/local, or some other such shared location.
> ...
> My proposal is to set includedir=${prefix}/include/postgresql (instead of
> ${prefix}/include)
