Re: Database port changing issue

I'm sorry but this is wrong, localhost IS 127.0.0.1 and IS a fundamental
component of TCP/IP. UNIX Domain sockets - known to most as file
descriptors - are entirely different!

localhost != UNIX Domain sockets!

I wish people would read up on this to stop perpetuating the
misunderstanding of 'localhost' and UNIX domain sockets.

From below, and from what another has already mentioned - that seems
more plausible - is that with the listen_address = '*' and with IPv6
enabled, there is potentially a confliect there.

Guido Barosio wrote:

> That's because your listen_addresses parameter points to localhost,
> and that means that your will listen for connections through unix
> sockets instead of via TCP/IP.
>
> In order to change this, you'll need to replace the string localhost
> with the proper value. (A bad habit, to replace the 'localhost' with a
> '*').
>
> Read the man page :)
>
> # - Connection Settings -
> listen_addresses = 'localhost' # what IP address(es) to listen on;
>
> # Would be something like:
> listen_addresses = '*'
>
> Best wishes,
> Guido
>
>
>
>
>
>
>
> On 6/9/06, Mohamed Fazil <mohdfazil_p_a(at)yahoo(dot)com> wrote:
>
>>
>> Hi to all,
>>
>> I am facing an issue while changing database port in the new version
>> 8.1.
>> The previous version which i used was 7.3 and for the port change i
>> used to
>> change in postgresql.conf
>>
>> From PG 7.3
>> #---------------------------------------------------------------------------
>>
>> # CONNECTIONS AND AUTHENTICATION
>> #---------------------------------------------------------------------------
>>
>> # - Connection Settings -
>> #tcpip_socket = false
>> #max_connections = 100
>> # note: increasing max_connections costs about 500 bytes of shared
>> # memory per connection slot, in addition to costs from shared_buffers
>> # and max_locks_per_transaction.
>> #superuser_reserved_connections = 2
>> port = 5432
>> #unix_socket_directory = ''
>> #unix_socket_group = ''
>> #unix_socket_permissions = 0777 # octal
>> #virtual_host = '' # what interface to listen on; defaults to any
>> #rendezvous_name = '' # defaults to the computer name
>> # - Security & Authentication -
>> #authentication_timeout = 60 # 1-600, in seconds
>> #ssl = false
>> #password_encryption = true
>> #krb_server_keyfile = ''
>> #db_user_namespace = false
>>
>>
>> Now for the port change in the newer version i tried to change the
>> same as
>> shown below in postgresql.conf.
>>
>> From PG 8.1
>> #---------------------------------------------------------------------------
>>
>> # CONNECTIONS AND AUTHENTICATION
>> #---------------------------------------------------------------------------
>>
>> # - Connection Settings -
>> listen_addresses = 'localhost' # what IP address(es) to listen on;
>> # comma-separated list of addresses;
>> # defaults to 'localhost', '*' = all
>> port = 5478
>> max_connections = 100
>> # note: increasing max_connections costs ~400 bytes of shared memory per
>> # connection slot, plus lock space (see max_locks_per_transaction). You
>> # might also need to raise shared_buffers to support more connections.
>> #superuser_reserved_connections = 2
>> #unix_socket_directory = ''
>> #unix_socket_group = ''
>> #unix_socket_permissions = 0777 # octal
>> #bonjour_name = '' # defaults to the computer name
>> # - Security & Authentication -
>> #authentication_timeout = 60 # 1-600, in seconds
>> #ssl = off
>> #password_encryption = on
>> #db_user_namespace = off
>> # Kerberos
>> #krb_server_keyfile = ''
>> #krb_srvname = 'postgres'
>> #krb_server_hostname = '' # empty string matches any keytab entry
>> #krb_caseins_users = off
>> # - TCP Keepalives -
>> # see 'man 7 tcp' for details
>> #tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds;
>> # 0 selects the system default
>> #tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds;
>> # 0 selects the system default
>> #tcp_keepalives_count = 0 # TCP_KEEPCNT;
>> # 0 selects the system default
>>
>> But i am getting an error as mentioned below
>>
>> org.postgresql.util.PSQLException: Connection refused.
>> Check that the hostname and port are correct and that the postmaster is
>> accepting TCP/IP connections.
>>
>> What are the changes that i have to do for changing port.
>>
>> If i am replacing it to 5432, it is working fine.
>>
>> I had a great support and help from this mailing team and i expect
>> the same.
>>
>> Thanks to all in advance.
>>
>> Regards
>>
>> Mohamed Fazil
>>
>>
>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>
>
>