A refinement: what if we only change behavior when target_session_attrs is explicitly set to something other than any?
-1. That seems to complicate things further, and still doesn't make our code match our docs
resolving to both "127.0.0.1" and "::1",
Bit of a contrived case, but I'm not really seeing the problem here. It's certainly possible for postgres to be listening on one and not the other, and if you want to connect to a specific one, then call it out by name. Otherwise, they all get tried, which is the whole reason the Internet has those one to many mappings. To give up after the first one fails seems inherently wrong.
