Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> Create a small program that makes a few connections to postgresql, does
> some initialization, preconnects to various DBs (or maybe limited to one DB
> specified on startup), and listens on one port/socket. It might not even
> prefork, just cache connections so first connection is slow, subsequent
> ones are cached along with the user-pass for faster authentication.
> Then your apps can connect to that small program, authenticate, and get the
> relevant connection. Call it a "Listener" if you want ;).
Couple of problems...
(a) where is this outside program going to get authentication
information from?
(b) it seems that not only the authentication exchange, but also all
subsequent data exchange of each connection would have to go through
this additional program. That middleman is going to become a
bottleneck.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
