From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "J(dot) Michael Roberts" <mirobert(at)cs(dot)indiana(dot)edu> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] IPC Memory problem with Postmaster on BSDi 4.x |
Date: | 1999-08-02 03:50:58 |
Message-ID: | 29774.933565858@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"J. Michael Roberts" <mirobert(at)cs(dot)indiana(dot)edu> writes:
> Since this was my first time compiling/installing pgsql, I've noticed a
> couple of oopses (maybe mine) in the installation instructions... Who do
> I talk to to update them? (Example: Instead of being able simply to type
> "initdb" to get started, I had to specify a user with "initdb -u
> postgres". That kind of stuff.)
FWIW, I think I know the cause of that one --- initdb, and also the
regression tests (and maybe other places?) look at the USER environment
variable by default to get the name of the postgres user. If you are
on a platform that doesn't ordinarily set USER, you lose. I've been
burnt by that myself.
I am not sure whether we ought to make the code look at LOGNAME as
a fallback if USER isn't set, or just document that you ought to set
USER. The first sounds good, but I wonder what the odds are of
picking up the wrong username. On my platform, for example, su'ing
to the postgres account does *not* change LOGNAME, which would mean
initdb would pick the wrong thing. Maybe what we need is just a
better error message ("USER environment variable is not set, please
set it or provide -u switch" ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | J. Michael Roberts | 1999-08-02 03:53:22 | Re: [HACKERS] Installation procedure. |
Previous Message | Thomas Lockhart | 1999-08-02 03:32:49 | Re: [HACKERS] Installation procedure. |