Re: optimizing db for small table with tons of updates
От | Kenji Morishige |
---|---|
Тема | Re: optimizing db for small table with tons of updates |
Дата | |
Msg-id | 20060403192851.GB15302@juniper.net обсуждение исходный текст |
Ответ на | Re: optimizing db for small table with tons of updates (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | 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@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
В списке pgsql-performance по дате отправления: