Re: [HACKERS] initdb problems on Solaris

From: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk>
To: hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] initdb problems on Solaris
Date: 2000-01-19 23:55:41
Message-ID: 200001192355.XAA12300@mtcc.demon.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

OOps,

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

From: Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-20 00:05:27 Re: [HACKERS] initdb problems on Solaris
Previous Message Keith Parks 2000-01-19 23:41:21 initdb problems on Solaris