Re: optimizing db for small table with tons of updates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Kenji Morishige <kenjim(at)juniper(dot)net>, pgsql-performance(at)postgresql(dot)org
Subject: Re: optimizing db for small table with tons of updates
Date: 2006-04-03 19:23:50
Message-ID: 15871.1144092230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kenji Morishige 2006-04-03 19:28:51 Re: optimizing db for small table with tons of updates
Previous Message Kenji Morishige 2006-04-03 19:08:36 Re: optimizing db for small table with tons of updates