From: | Kenji Morishige <kenjim(at)juniper(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org, kenjim(at)juniper(dot)net |
Subject: | Re: optimizing db for small table with tons of updates |
Date: | 2006-04-03 19:28:51 |
Message-ID: | 20060403192851.GB15302@juniper.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Quinn | 2006-04-03 21:24:48 | The order of fields around the "=" in the WHERE conditions |
Previous Message | Tom Lane | 2006-04-03 19:23:50 | Re: optimizing db for small table with tons of updates |