On Wed, Jul 21, 2010 at 11:13 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Jul 22, 2010 at 11:57 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Should we be using is_absolute_path() here instead, as libpq does?
> Yes. The attached patch does that.
>>> On Wed, Jul 21, 2010 at 10:09 PM, David Christensen <david(at)endpoint(dot)com> wrote:
>>> If we print the local socket when it's been explicitly set via the host= param, why not display the actual socket path in the general local socket case?
> Done. DEFAULT_PGSOCKET_DIR (i.e., /tmp) should be displayed in that
> case, I think.
> $ psql -c"\conninfo"
> You are connected to database "postgres" via local socket on
> "/tmp" at port "5432" as user "postgres".
Sorry for the slow response, I've been slightly buried.
I've committed this with some kibitzing, the most relevant bit of
which is that I changed "via local socket on" to "via local socket
in", which I think reads better.
The Enterprise Postgres Company
In response to
pgsql-hackers by date
|Next:||From: Jaime Casanova||Date: 2010-07-23 15:05:11|
|Subject: Re: including backend ID in relpath of temp rels - updated patch|
|Previous:||From: Tom Lane||Date: 2010-07-23 14:11:36|
|Subject: Re: [HACKERS] Trouble with COPY IN |