"S -" <nat_lazy@hotmail.com> writes:
> In our project, we have unix socket networking going on and the Postgresql
> code is the server in this process. We would want the postgresql database to
> run as usual while it is transferring data (as a server) to another program
> (the client, in our case, a GUI). Therefore, we would want to fork another
> process that acts as the server.
What exactly is this doing that's different from having two separate
database connections served by two backend processes?
regards, tom lane
