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:
> A
Alvaro Herrera <[EMAIL PROTECTED]> 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
Sweet! Thanks.
-Kenji
On Mon, Apr 03, 2006 at 03:03:54PM -0400, Alvaro Herrera wrote:
> 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
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 wonder
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
Kenji Morishige <[EMAIL PROTECTED]> writes:
> Various users run a tool that updates this table to determine if the
> particular
> resource is available or not. Within a course of a few days, this table can
> be updated up to 200,000 times. There are only about 3500 records in this
> table, but t
Dear Kenji,
we had similar issuse with a banner impression update system,
that had high concurrency. we modfied the system to use insert
instead of update of the same row. performance wise things are
much better , but you have to keep deleting old data.
hope you extrapolate what i mean if its app
Kenji,
> We used to use MySQL for these tools and we never had any issues, but I
> believe it is due to the transactional nature of Postgres that is adding
> an overhead to this problem.
You're correct.
> Are there any table options that enables
> the table contents to be maintained in ram on
I am using postgresql to be the central database for a variety of tools for
our testing infrastructure. We have web tools and CLI tools that require access
to machine configuration and other states for automation. We have one tool that
uses a table that looks like this:
systest_live=# \d cuty
