DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=ZcoloV32zImCL0i8XGP2daXpofebFdEMUY5nUUt1RwUl/MJb5tFFIS0eXZr0UDVibH
	rntSIwIXq8YjlIA5EHMxtn7gPhBLtyZJEoQPex4kiWQo21gp9RryQilLgQJ3InlLkIcn
	ymgGFmgPHiB3EXjRW2wfTmDTecpYdpUhbBO4A=
Message-ID: <fd145f7d0807221335l3a105df4v1d963d981792b8b4@mail.gmail.com>
Date: Tue, 22 Jul 2008 13:35:26 -0700
From: "Jeffrey Baker" <jwbaker@gmail.com>
To: "Greg Sabino Mullane" <greg@turnstep.com>
Subject: Re: Perl/DBI vs Native
Cc: pgsql-performance@postgresql.org
In-Reply-To: <dd0f5dcec7cfaac867cb7ce16c4ee3bf@biglumber.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <698916.49812.qm@web25803.mail.ukl.yahoo.com>
	<dd0f5dcec7cfaac867cb7ce16c4ee3bf@biglumber.com>

On Tue, Jul 22, 2008 at 9:48 AM, Greg Sabino Mullane <greg@turnstep.com> wrote:
>> In case someone is wondering, the way to force DBI to use unix
>> sockets is by not specifying a host and port in the connect call.
>
> Actually, the host defaults to the local socket. Using the port
> may still be needed: if you leave it out, it simply uses the default
> value (5432) if left out. Thus, for most purposes, just leaving
> the host out is enough to cause a socket connection on the default
> port.

For the further illumination of the historical record, the best
practice here is probably to use the pg_service.conf file, which may
or may not live in /etc depending on your operating system.  Then you
can connect in DBI using dbi:Pg:service=whatever, and change the
definition of "whatever" in pg_service.conf.  This has the same
semantics as PGSERVICE=whatever when using psql.  It's a good idea to
keep these connection details out of your program code.

-jwb