Re: unix_socket_directory bug or feature?

A yoda look alike informed me that I should use -h which does work.

Joshua D. Drake wrote:
> Hello,
>
> unix_socket_direct = '/tmp/foo'
> unix_socket_group = 'postgres'
> unix_socket_permission = '0200'
>
> -bash-3.00$ bin/pg_ctl -D /usr/local/pgsql/etc/ start
> postmaster starting
> -bash-3.00$ LOG: could not open Ident usermap file
> "/usr/local/pgsql/etc/pg_ident.conf": No such file or directory
> LOG: database system was shut down at 2005-05-06 14:46:39 PDT
> LOG: checkpoint record is at 0/A32BD4
> LOG: redo record is at 0/A32BD4; undo record is at 0/0; shutdown TRUE
> LOG: next transaction ID: 545; next OID: 17230
> LOG: database system is ready
>
> -bash-3.00$ bin/psql -U postgres template1
> psql: could not connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
> -bash-3.00$
>
> psql is looking in the wrong directory for the socket.
>
> -bash-3.00$ bin/psql -U postgres -h 127.0.0.1 template1
> Welcome to psql 8.0.2, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> template1=#
>
> Sincerely,
>
> Joshua D. Drake
>
>

--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedication Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/