This is the section concerning connection parameters of the /var/lib/pgsql/data/postgresql.conf file. It works fine on my server.
There are many other options in this conf file. The best thing to do is to read the Admin manual, if you want to understand the meaning of these parameters.
fred
#
# Connection Parameters
#
tcpip_socket = true
#ssl = false
max_connections = 5
port = 5432
hostname_lookup = false
show_source_port = false
unix_socket_directory = '/tmp'
unix_socket_group = 'postgres'
unix_socket_permissions = 0777
#virtual_host = ''
#krb_server_keyfile = ''
#
# Shared Memory Size
#
Daniel WELLS a écrit:
O.K. so how I got the problem fixed will be broken again if U get an update. The original question still hasn't been answered then. You say to configure the TCP socket . . .
Can you please be a little more forthcoming as to how this is done?
yinyang@eburg.com 11/22/02 10:15AM >>>On Thu, 2002-11-21 at 23:57, FredBriand wrote:I may mystake because I configured my serveur some times ago (i'm still using RH73!) and that's not the kind of thing I modify for fun, but if I remember well, and I think I do, postgresql's default conf is not to accept tcp/ip connections. If you wish to, just modify pg_hba.
pg_hba.conf configures access control mechanisms. postgresql.conf configures daemon options, such as whether or not to listen on the TCP port.Yet if it still does'nt work, I suppose you can add the -i in the /etc/init.d/postgresql.
Bad idea: updates or errata will replace the init file, and interrupt service. Configure the TCP socket where it's supposed to be configured, and the future will bring you less trouble.
-- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
