To echo Jeff: It is intentional behavior. There are sites that don't want postmaster listening on a TCP/IP socket for security reasons; these sites have a way of using the pg driver using only unix sockets. Incidentally, PostgreSQL 'out of the box' is set to only listen to local unix sockets -- you have to change the options in postgresql.conf (or use the older '-i' switch to postmaster) to make it listen to the TCP/IP socket. That also is intentional.
Having said that, having the connect fall through to the TCP/IP connection makes some sense; I'll see if I can't get it do to that soon, without creating a different security issue.
Incidentally, PostgreSQL supports direct SSL connections. I haven't tried using them from AOLserver, however. f anyone else has gotten that to work, it would be nice to know.
