I will be querying the machine from another host. When postgres starts upon bootup, it does not setup for port 5432. I have to manually go in and type postmaster -p 5432 (directory) However, my posgresql.conf is set tcpip_socket = true and shows port 5432 in there....any suggestions?
Darryl -----Original Message----- From: Gordon Messmer [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 21, 2002 2:14 PM To: [EMAIL PROTECTED] Subject: RE: Postgres Startup On Thu, 2002-11-21 at 08:01, Delao, Darryl W wrote: > The main problem I am having is that postgres starts up fine, but does not > open port 5432 which is what I need for all of my local connections to be > able to talk to the database. I am new to this, so please bear with me. Is > there anything I can set to where it will open 5432 everytime postgres is > started? Heh... I just posted this to the psyche-list: Since the question was already answered, I'll suggest that when you direct your code to connect to the server, you simply do not provide a hostname. In this case, the SQL client will try to use the local UNIX socket, rather than TCP/IP. In this configuration, you do not expose the database server to remote network attacks. The default is ideal if you are running your SQL code and the server on the same machine. You should only turn on TCP/IP if you are actually querying the machine from a remote host. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
