Re: Bug in createlang?

Awesome. That is what I am looking for. I have been having a problem
restoring a database without changing the security options and restarting
the server. Real hassle. This could be what I am looking for. phpPgAdmin
is running on the same machine, should I just tell it to use the "public"
address instead of localhost so that authentication is still required for it
(without trying to use ident)?

Thanks,

Tom Veldhouse
veldy(at)veldy(dot)net

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Richard Huxton" <dev(at)archonet(dot)com>
Cc: "Thomas T. Veldhouse" <veldy(at)veldy(dot)net>; <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, June 27, 2001 9:24 AM
Subject: Re: [GENERAL] Bug in createlang?

> Richard Huxton <dev(at)archonet(dot)com> writes:
> > "Thomas T. Veldhouse" wrote:
> >> Why does it ask 4 times?
>
> > createlang is just a script - it basically runs "/path/to/psql $QUERY" -
> > each query connects a separate time.
>
> Note that running a setup that requires password auth for the DBA will
> also be a major pain in the rear when running pg_dumpall: one password
> prompt per database, IIRC. We have other scripts that make more than
> one database connection, too.
>
> I'd counsel using a setup that avoids passwords for local connections.
> One way to do this is to run an ident daemon and use IDENT authorization
> for connections from 127.0.0.1. This allows "psql -h localhost" to work
> without a password. (IDENT authorization is quite properly discouraged
> for remote connections, but it's trustworthy enough on your own machine,
> if you control the ident daemon or trust the person who does.)
>
> regards, tom lane
>