Re: [HACKERS] initdb problems on Solaris - Mailing list pgsql-hackers

From Keith Parks
Subject Re: [HACKERS] initdb problems on Solaris
Date
Msg-id 200001192355.XAA12300@mtcc.demon.co.uk
Whole thread Raw
Responses Re: [HACKERS] initdb problems on Solaris
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Keith Parks
Date:
Subject: initdb problems on Solaris
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] initdb problems on Solaris