Re: postgres on SuSE 9.1 - Mailing list pgsql-general

From Bill Moran
Subject Re: postgres on SuSE 9.1
Date
Msg-id 20040607130408.33f16959.wmoran@potentialtech.com
Whole thread Raw
In response to postgres on SuSE 9.1  (Prabu Subroto <prabu_subroto@yahoo.com>)
Responses Re: postgres on SuSE 9.1
List pgsql-general
Prabu Subroto <prabu_subroto@yahoo.com> wrote:

> Dear my friends...
>
> Usually I use MySQL. Now I have to migrate my database
> from MySQL to Postgres.
>
> I have created a database successfully with "creatdb"
> and a user account successfully.
>
> But I can not access the postgres with pgaccess.
>
> I found this error message :
> "
> Error trying to connect to database 'custadm' on host
> localhost
>
> PostgreSQL error message: Connection to database
> failed
> could not create socket: __H____pH____lH____
> "
> Error in startup script: window ".pgaw:OpenDB" was
> deleted before its visibility changed
>     while executing
> "tkwait visibility .pgaw:OpenDB"
>     (procedure "::Connections::openConn" line 40)
>     invoked from within
> "::Connections::openConn $i 1"
>     (procedure "main" line 63)
>     invoked from within
> "main $argc $argv"
>     (file "/usr/bin/pgaccess" line 810)
> patrixlinux@patrix:~>
> "
>
> Here what I have done
> "
> patrixlinux@patrix:~> su
> Password:
> patrix:/localhome/patrixlinux # su postgres
> postgres@patrix:/localhome/patrixlinux> cd
> postgres@patrix:~> psql custadm
> Welcome to psql 7.4.2, the PostgreSQL interactive
> terminal.
>
> Type:  \copyright for distribution terms
>        \h for help with SQL commands
>        \? for help on internal slash commands
>        \g or terminate with semicolon to execute query
>        \q to quit
>
> custadm=# create user someone with password 'pass_me'
> createdb;
> CREATE USER
> custadm=#
> "
>
> Anybody would be so nice to tell me why I can not
> access my postgres with pgaccess?
>
> Thank you very much in advance.

I would guess that Posgres is not listening on an IPv4 socket.  I think pgaccess
always connects via an IPv4 socket.  (may be wrong here ...)

Anyway, check your postgresql.conf file to see if the option to listen on a
tcp/ip port is turned on.  If not, that's almost definately your problem.

--
Bill Moran
Potential Technologies
http://www.potentialtech.com

pgsql-general by date:

Previous
From: Lincoln Yeoh
Date:
Subject: Re: Index question
Next
From: Jeff Boes
Date:
Subject: Re: Timestamp precision and rounding