OOps,

Just noticed we no longer have trusty "pg_id".....


From: Keith Parks <emkxp01@mtcc.demon.co.uk>

>Hi All,
>
>I know that the whole "id" thing in initdb is a can of worms.
>We have pg_id but we don't want to use it, every system has 
>a different version/variety of whoami/"who am i"/id.
>
>We don't need/want to use the unix ID of the user, but we do
>when we can. The whole thing is a mess!!
>
>One thing we need to do is change the default, "if all else
>fails" id from 0 to something else, as 0 is specifically 
>disallowed and causes an "Abort" in postgres when bootstrapping.
>
>Here's a patch to set it to 1. ( failing any better suggestion)
>
>Keith.


Wed, 19 Jan 2000 23:55:41 +0000 (GMT)
Keith Parks <emkxp01@mtcc.demon.co.uk>
Re: [HACKERS] initdb problems on Solaris
On Wed, 19 Jan 2000, Keith Parks wrote:

> Just noticed we no longer have trusty "pg_id".....

Wasn't needed any longer. However, with the persisting problems on
Solaris, I am tempted to take the 'id' command from FreeBSD (which seems
to be POSIX compliant) and reinstitute it as new pg_id. That would also
solve the whoami problem (the reverse if what pg_id did).

Any protests? Otherwise I'll get this fixed.

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


Thu, 20 Jan 2000 12:24:19 +0100 (MET)
Peter Eisentraut <e99re41@DoCS.UU.SE>
Re: [HACKERS] initdb problems on Solaris