Subject: Re: Embedding postgresql in my application
From: Murray Cumming <murrayc@murrayc.com>
To: "Jeroen T. Vermeulen" <jtv@xs4all.nl>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
In-Reply-To: <20058.125.24.243.222.1166249768.squirrel@webmail.xs4all.nl>
References: <1166225144.12609.2.camel@localhost.localdomain>
	<20058.125.24.243.222.1166249768.squirrel@webmail.xs4all.nl>
Content-Type: text/plain
Date: Tue, 19 Dec 2006 16:36:53 +0100
Message-Id: <1166542613.20613.19.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Sat, 2006-12-16 at 13:16 +0700, Jeroen T. Vermeulen wrote:
> f your application
> can run under many different user identities and each should have its
> own
> database user, use "ident sameuser"

I believe that ident authentication requires an additional service such
as gidentd. Well, I think that's been my experience in the past.

>  and create a database user for every
> system user when that user first runs the application:
> 
>   createuser -h "$DBDIR/data" \
>     --no-superuser \
>     --no-createrole \
>     --no-createdb \
>     $USERNAME 

createuser asks for a password on stdin. Do you know of any way to
specifify an initial superuser and password for a new database cluster
without doing it via stdin? That doesn't seem like a stable API that I
should rely on.

-- 
Murray Cumming
murrayc@murrayc.com
www.murrayc.com
www.openismus.com