Re: embedded postgresql

On Nov 14, 2003, at 14:13, jini us wrote:

> I would class your solution as a work around
> rather than a "natural solution".

	It really seemed like the obvious way to do it (I'm sure I'm not the 
only person who thought of that, but didn't post it).

> Anyway I am using  MS windows and to implement
> postgres as embedded, using your approach, would
> probably become complicated.
> .It would probably introduce unwanted bugs in my
> software.

	I believe it would be you introducing those bugs if you do not 
initialize the DB correctly, regardless of the mechanism.

	Now, how many bugs do you think it would create in postgres if the 
entire interface model were changed from postmaster/postgres processes 
to having multiple threads in a single application trying to issue 
queries in the in-process DB.  What happens to the DB when your app 
segfaults?  Are there any signal handlers postgres uses that you would 
want to use in your app?  Do you really need to redesign the way 
postgres works just because you don't want to manage the resource as a 
process rather than a different type of API?

-- 
Dustin Sallings