Thread: PostgreSQL/PGAdmin service hangs when listen_addresses = '*'

After changing the listen_address to '*' I told PGAdmin to stop the
service, then to start it.
Then when I tried to connect to the database PGAdmin just hanged. The
service wouldn't stop afterward and I had to restart. I tried several
times with the same result.

Changing the listen_addresses to 'localhost' and even to 'localhost,*'
and following the same procedure with PGAdmin works fine.

Anyone can confirm this? Why is it happening?

PostgreSQL 8.0.0rc1
PGAdmin 1.2.0 Post-RC2 (Nov 20 2004)

--
 ICQ: 1912453
 AIM: VitalyB1984
 MSN: tmdagent@hotmail.com
 Yahoo!: VitalyBe

what shows up in the server log?

If that parameter is in error you should see messages like this:

  could not create listen socket for "foo"

(Is there a windows utility that does the equivalent of netstat -a? How
does one see what is being listened to?)

cheers

andrew

Vitaly Belman wrote:

>After changing the listen_address to '*' I told PGAdmin to stop the
>service, then to start it.
>Then when I tried to connect to the database PGAdmin just hanged. The
>service wouldn't stop afterward and I had to restart. I tried several
>times with the same result.
>
>Changing the listen_addresses to 'localhost' and even to 'localhost,*'
>and following the same procedure with PGAdmin works fine.
>
>Anyone can confirm this? Why is it happening?
>
>PostgreSQL 8.0.0rc1
>PGAdmin 1.2.0 Post-RC2 (Nov 20 2004)
>
>
>

> (Is there a windows utility that does the equivalent of netstat -a? How
> does one see what is being listened to?)

In XP pro, it's 'netstat' :)

To see which program is listening, use the '-o' option to list pids, then
use task manager to get the process name from the pid (you'll have to select
the pid field to be displayed via view->Select Columns...).


Christian