Bruce Momjian <[EMAIL PROTECTED]> writes: >> On some operating systems, only one child at a time can accept() on the >> socket. On these, you have to lock around the call to accept().
> But how do you know the client wants the database you have forked? They > could want a different one. This approach would only work as far as saving the fork() call itself, not the backend setup time. Not sure it's worth the trouble. I doubt that the fork itself is a huge component of our start time; it's setting up all the catalog caches and so forth that's expensive. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster