[HACKERS] problems with sunos4 port, endian?
| От | Chris McGonagle |
|---|---|
| Тема | [HACKERS] problems with sunos4 port, endian? |
| Дата | |
| Msg-id | 436fc228e0eb3142ce0f052b6923fa75 обсуждение исходный текст |
| Список | pgsql-hackers |
I've been plagued with a connectivity problem to my PostgreSQL database running on a Sparc Sun4 (SunOS 4.1.4) box (both May and 6.1 release versions). I've been trying to use the postODBC drivers and also the pre-built psql.exe client (both under NT) against the sun with no success. The same ODBC and psql programs connect flawlessly to a copy of PostgreSQL running on a FreeBSD box (i386, pg version is dated sometime January). Until today, I figured it was probably some change made to the protocol since the January build which was breaking the earlier compiled clients. However, now I have a situation where I used gcc-cygwin32 to build the psql.exe straight from the 6.1 release source - thereby ensuring my PC client is up to date with the sun server. Suprisingly, the psql.exe file still refused to work with my sun4 box. It worked flawlessly with the FreeBSD box. I've been accessing the database on the sun4 with only 'localhost' connects and I have otherwise had no other problems with the system. The clients on the PC are able to discriminate between valid and invalid database/pguser names. Any form of query or such commands as '\d' or '\l' will sit there forever. ------------------------------
В списке pgsql-hackers по дате отправления: