From: Christopher Browne <cbbrowne@acm.org>
Subject: Re: running PostGres without installing it
Date: Sun, 06 Aug 2006 21:47:39 -0400
Organization: cbbrowne Computing Inc
Lines: 26
Message-ID: <8764h5wc3o.fsf@wolfe.cbbrowne.com>
References: <20060806040747.99775.qmail@web32509.mail.mud.yahoo.com>
	<bf05e51c0608061109x368a06b3uec4a7c5ff38ff58e@mail.gmail.com>
	<1154891491.3403.11.camel@workstation01.barsandtone.com>
	<bf05e51c0608061313h28973179nee1b094e660cff26@mail.gmail.com>
	<1154912482.3403.23.camel@workstation01.barsandtone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux)
Cancel-Lock: sha1:q71zIwHq/AjXd8bXK0+15h6j0Y0=
To: pgsql-admin@postgresql.org

amadeus0@cox.net (Amadeus Zilfinski) wrote:
> My only real issue with PostgresQL is that it is a client/server
> database, that is not embeddable. If it was embeddable then I could
> use it with no issue, and would in fact rather use it. I recall some
> people are working on that, but don't have any links. You might want
> to try www.postgresql.org and see if they any info on there.

No, there is *not* an a set of people working on "making PostgresQL
embeddable"; it has been talked about, but never taken particularly
seriously.

There's a way to do *a sort of embedding*, but one that specifically
ignores the notion of doing this in an in-process manner.

You could hide a PostgresQL instance, using a variant port, generally
making it pretty hidden away.  Initializing, starting, and stopping it
could be hidden inside the application.

But in no way would this be an embedding as is normally understood,
where all that's needful is to include a library and open the right
directory.
-- 
select 'cbbrowne' || '@' || 'gmail.com';
http://linuxdatabases.info/info/lisp.html
"Bureaucracies interpret communication as damage and route around it"
-- Jamie Zawinski