Skip site navigation (1) Skip section navigation (2)

Re: Perl/DBI vs Native

From: "Jeffrey Baker" <jwbaker(at)gmail(dot)com>
To: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Perl/DBI vs Native
Date: 2008-07-22 20:35:26
Message-ID: fd145f7d0807221335l3a105df4v1d963d981792b8b4@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Tue, Jul 22, 2008 at 9:48 AM, Greg Sabino Mullane <greg(at)turnstep(dot)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

In response to

Responses

pgsql-performance by date

Next:From: Jeffrey W. BakerDate: 2008-07-23 00:04:35
Subject: Samsung 32GB SATA SSD tested
Previous:From: samantha mahindrakarDate: 2008-07-22 18:59:55
Subject: Re: Performance of jobs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group