| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tim Barnard <tbarnard(at)povn(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: 7.1beta4 initdb problem |
| Date: | 2001-02-05 19:05:46 |
| Message-ID: | 17616.981399946@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Probably initdb should have its own check for being run as root;
>> this seems cleaner than reorganizing the checks in the postgres
>> executable.
> I does have that check, but unfortunately that check requires pg_id, and
> finding the right pg_id requires finding the right postgres. The "right
> pg_id" is not entirely as trivial as it sounds, because pg_id's from <=6.5
> have very different behaviour.
Um. Okay then, the alternatives are
(1) move the handling of --version out of PostgresMain and friends, and
put it into main.c before the are-we-root check;
(2) move the are-we-root check out of main.c and duplicate it in
PostgresMain and friends.
Which choice do you like best?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kovacs Baldvin | 2001-02-05 19:13:38 | Re: [HACKERS] Re: Re: grant privileges to a database [URGENT] |
| Previous Message | Peter Eisentraut | 2001-02-05 18:00:44 | Re: 7.1beta4 initdb problem |