Name Lookup Weirdness
От | Holger Klawitter |
---|---|
Тема | Name Lookup Weirdness |
Дата | |
Msg-id | 200411051442.40153.lists@klawitter.de обсуждение исходный текст |
Ответы |
Re: Name Lookup Weirdness
Re: Name Lookup Weirdness |
Список | pgsql-jdbc |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I have made a very weird observation with JDBC. After a major machine upgrade postgres 7.3.4 no longer accepts JDBC connection requests *of a certain kind*: jdbc:postgresql://my.host.name/dbname works jdbc:postgresql://127.0.0.1/dbname works jdbc:postgresql://localhost/dbname does not work?! jdbc:postgresql:dbname does not work psql dbname works psql -h localhost dbname works It seems to be independant of the JVM (tried 1.4.2 and 1.5.0) the postgres binary (and config) itself did not change over the upgrade. Everything else on that machine as been pretty much turned upside down. (Linux 2.2 -> Linux 2.6, et al ;-) I tried postgresql.jar of 7.3.2 and 7.3.4. I know how to circumvent the problem (and I'll go 8.0 on that machine quite soon as well), but I would like to know if anyone else has seen such a thing... Mit freundlichem Gruß / With kind regards Holger Klawitter - -- lists <at> klawitter <dot> de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFBi4NP1Xdt0HKSwgYRAt7JAKCYaboztyYu6wWQZEwS+pRzmeWeQwCfaw8R 24FzFMy1uF3cZ+Rr/Ro4rnA= =uPwa -----END PGP SIGNATURE-----
В списке pgsql-jdbc по дате отправления: