Re: initdb.sh fixed - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: initdb.sh fixed
Date
Msg-id Pine.LNX.4.21.9912190127480.356-100000@localhost.localdomain
Whole thread Raw
In response to Re: initdb.sh fixed  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [HACKERS] Re: initdb.sh fixed7
Re: initdb.sh fixed
List pgsql-hackers
On 1999-12-18, Bruce Momjian mentioned:

> The big problem seems to be reliance on bash-isms like $UID and
> functions with spaces like:

Bash tells me that is it's invoked as 'sh' it will behave like 'sh', but
it's lying ...

> > 'insert ( data data data )' bootstrap commands are containing gaps. On the
> > other hand, this was one of the key things that were supposed to be
> > improved because relying on $USER was not su-safe. Maybe $UID would work,
> > since initdb isn't supposed to be setuid anyway.
> 
> Again, a bash-ism.  Let's face, it, the postgres binary is going to
> croak on root anyway, so we are just doing an extra check in initdb.

But the point was to initialize to superuser id in Postgres as that
number, but we might as well start them out at 0, like it is now.

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] Lock
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock