From: | alex avriette <alex(at)posixnap(dot)net> |
---|---|
To: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql inability to select a socket |
Date: | 2003-05-11 19:13:11 |
Message-ID: | 9B59D704-83E4-11D7-A4F1-003065BDE8A6@posixnap.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> AFAIK there's a special case for "hostnames" with slashes; those get
> interpreted as a path to a local socket. Try setting PGHOST to
> /var/www/tmp before you start psql, for instance.
Ah! Jeroen this is wonderful. Thank you.
stink# setenv PGHOST /var/www/tmp
stink# /var/postgresql/bin/psql -U snort snort
Welcome to psql 7.3.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
snort=>
My mistake, I didn't RT the FM:
--host hostname
Specifies the host name of the machine on which the
postmaster is running. If host begins with a slash,
it is used as the directory for the Unix-domain
socket.
Would it be overly verbose to mention the various PGHOST, PGDATA,
PGUSER, etc variables in the output of
`psql --help`?
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-11 20:01:44 | Re: SET CONSTRAINTS not schema-aware |
Previous Message | Oleg Bartunov | 2003-05-11 18:26:18 | tsearch upgrade documentation needed |