From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: serverless postgresql |
Date: | 2004-01-14 05:18:10 |
Message-ID: | m3zncrcdm5.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Quoth jlb(at)houseofdistraction(dot)com (Jeff Bowden):
> For ease of configuration and other reasons, I would like for my
> single-user GUI app to be able to use postgresql in-process as a
> library accessing a database created in the users home directory. I
> think I could possibly get what I want by launching a captive copy of
> postmaster with appropriate args but it seems conceptually cleaner to
> not have a seperate process at all. Has anyone tried to do anything
> like this?
One of the properties of Unix is that spawning extra processes to "do
their thing" allows each application to be designed more 'cleanly.'
Curiously enough, the implementors of alternatives to the Sendmail MTA
have typically concluded that it was not only conceptually cleaner to
have a set of separate cooperating processes, but that they would also
reap benefits in terms of speed and improved security.
Thus, I think you'll find that people disagree with you on this. It
seems to me that it is conceptually cleaner to have the "application"
do "application stuff," and not muddle things up by mixing that with
the "database stuff."
--
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne> rate me
http://cbbrowne.com/info/sgml.html
Rules of the Evil Overlord #87. "My vats of hazardous chemicals will
be covered when not in use. Also, I will not construct walkways above
them." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2004-01-14 05:43:07 | Re: Best practice? Web application: single PostgreSQL |
Previous Message | Jeff Bowden | 2004-01-14 05:13:00 | Re: serverless postgresql |