Massa, Harald Armin wrote:
on unix, as you imply, it can be run with unix domain sockets,but not on Windows as they simply don't have this interface. and, it can be started as an application rather than as asystem service, but it still runs as a separate process from your application(s) and in my book, thats not really embedded.within Windows there is the concept of a "named pipe". You could dig into the communication code of Postgres which puts data through the unix-socket, and write an "named pipe" communicator. PostgreSQL would still be running in its own process, but only accessable from within the application. Be aware: that is an idea for a solution; it is neither included nor projected for PostgreSQL.
I'm not sure more than one connection can be made to a named pipe, they don't really work like sockets, so this would be a poor choice as even an embedded database typically needs several connects from a multithreaded application (plus maintenance connections such as autovacuum)
-- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
