Not quite correct. TCP needs to be turned on AND an according entry in pg_hba.conf needs to be set up - otherwise the server will just decline to talk to the client. Also - if you're on XP you might want to check the "firewall" settings - which if configured wrong could potentially block connections on port 5432. If you have a default setup of XP it should be fine though. On Wednesday 22 June 2005 08:56 pm, William Yu wrote: > There's nothing on the server side that needs to be configured for > Windows clients to access Postgres via ODBC. As long as TCP/IP is turned > on. Just add a data source and configure the server > ip/name/port/database/etc. > > SCassidy@xxxxxxxxxxxxxxxxxxx wrote: > > Hi, > > I have seen a bunch of different documentation on how to set up to allow > > ODBC, but I am a little confused about how much/what has to be set up to > > allow an ODBC connection from Windows (mostly 2003, some XP) to an > > existing PostgreSQL (7.4.6) database on Linux (RedHat 9 version > > 2.4.20-6smp). > > > > Most of the documentation is talking about setting up Unix to Unix odbc, > > or Windows to Windows, not Windows to Unix/Linux. > > > > Some documentation talks about installing the "full" distribution on > > Windows, but I just want to allow some Windows software that "speaks" > > ODBC (SilkTest) to be able to connect to an existing database. > > > > > > In the document > > http://gborg.postgresql.org/project/psqlodbc/genpage.php?howto-redhat, > > it says to download rpms and install them, but I don't really see any > > rpms for this. I see source distributions at > > http://www.postgresql.org/ftp/odbc/versions/src/, but nothing for version > > 7.4, just 7.3 and 8.0. I am reluctant to upgrade to 8.0, as I am not > > sure it is stable yet, and my installation is running so well. > > > > > > The howto-redhat document also talks about running: > > > > > > > > > > psql -d template1 -f /usr/share/pgsql/odbc.sql > > > > > > > > > > > > to modify template1, but what about existing databases? > > > > I'm somewhat nervous about doing anything to potentially mess up anything > > on my Linux server, as this is a production database. > > > > Then, you have to set up the iodbc driver manager, etc. On this server, > > I have had some issues with using rpm's in the past, and have often had > > to resort to building things myself (configure, make, etc.) > > > > I'm also not sure about how to specify a DSN to do the connection from > > the Windows side (I'm primarily a Unix/Linux person). > > > > Does anyone have any specific advice/experiences to offer on setting this > > up as simply as possible? > > > > Thanks, > > Susan > > > > > > > > > > ------------------------------------------------------------------------- > >--------------------- See our award-winning line of tape and disk-based > > backup & recovery solutions at http://www.overlandstorage.com > > ------------------------------------------------------------------------- > >--------------------- > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your > > message can get through to the mailing list cleanly > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your > message can get through to the mailing list cleanly -- UC -- Open Source Solutions 4U, LLC 2570 Fleetwood Drive Phone: +1 650 872 2425 San Bruno, CA 94066 Cell: +1 650 302 2405 United States Fax: +1 650 872 2417 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
