> -----Original Message-----
> From: pgadmin-hackers-owner@postgresql.org
> [mailtogadmin-hackers-owner@postgresql.org] On Behalf Of
> cvs@developer.pgadmin.org
> Sent: 18 April 2005 15:39
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] CVS Commit by andreas: Unix Domain
> Socket additional stuff switch to
>
> Log Message:
> -----------
> Unix Domain Socket additional stuff

Err, would you mind unbreaking this please? I can no longer change the
port number for the socket (libpq uses it to form part of the filename),
and the trailing / that is added to the end of the path now results in
libpq trying to connect to paths such as /tmp//.s.PGSQL.5432, which
although it works, is not technically correct iirc.

Heavy night on the beer last night? :-)

/D

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Dave Page wrote:
>
> Err, would you mind unbreaking this please? I can no longer change the
> port number for the socket (libpq uses it to form part of the filename),

Uh, I wasn't aware of that. Hm, whatever this is good for...

> and the trailing / that is added to the end of the path now

This is your libpq's fault, I can't see any code to add a trailing /.
Your DEFAULT_PGSOCKET_DIR is probably "/tmp/".

Regards,
Andreas

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match