From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Kenji Morishige <kenjim@juniper.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: optimizing db for small table with tons of updates
Date: Mon, 03 Apr 2006 15:23:50 -0400
Message-ID: <15871.1144092230@sss.pgh.pa.us> (raw)
In-Reply-To: <20060403190354.GC15756@surnet.cl>
References: <20060403182403.GA12257@juniper.net>
<15521.1144089550@sss.pgh.pa.us>
<20060403190213.GA14328@juniper.net>
<20060403190354.GC15756@surnet.cl>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, kenjim@juniper.net
Subject: Re: optimizing db for small table with tons of updates
In-Reply-To: <15871.1144092230@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox