Date: Mon, 3 Apr 2006 12:28:51 -0700
From: Kenji Morishige <kenjim@juniper.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>,
	pgsql-performance@postgresql.org, kenjim@juniper.net
Subject: Re: optimizing db for small table with tons of updates
Message-ID: <20060403192851.GB15302@juniper.net>
References: <20060403182403.GA12257@juniper.net>
	<15521.1144089550@sss.pgh.pa.us>
	<20060403190213.GA14328@juniper.net>
	<20060403190354.GC15756@surnet.cl> <15871.1144092230@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15871.1144092230@sss.pgh.pa.us>
User-Agent: Mutt/1.4.2.1i

Cool, looks like I had tried the .pgpass thing a while back and wasn't working,
I realized I had a typo or something in there. It works like a charm. Security
in our intranet is not a big issue at the moment. Thanks for the help!
-Kenji

On Mon, Apr 03, 2006 at 03:23:50PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Kenji Morishige wrote:
> >> I've been stumped as to how to call psql from the command line without it 
> >> prompting me for a password. Is there a enviornoment variable I can specify for
> >> the password or something I can place in .pgsql?  I could write a perl wrapper
> >> around it, but I've been wondering how I can call psql -c without it prompting
> >> me. Is it possible?
> 
> > Sure it is.  Set up a .pgpass file.
> 
> Also, consider whether a non-password-based auth method (eg, ident)
> might work for you.  Personally, I wouldn't trust ident over TCP, but
> if your kernel supports it on unix-socket connections it is secure.
> 
> 			regards, tom lane