I hope the method with the environment variables will hold on. For security reasons it is much better to use the variable method with PGPASSWORD. I can set the environment hidden from any user by a program. The .pgpass is readable for any admin, opposed to the statement in the docs: "On Microsoft Windows, it is assumed that the file is stored in a directory that is secure, so no special permissions check is made."
Regards Walter On Wed, Jul 28, 2010 at 1:02 AM, Scott Marlowe <scott.marl...@gmail.com>wrote: > However, those are deprecated, and the .pgpass is considered the > preferred method. > > On Tue, Jul 27, 2010 at 3:56 PM, Walter Willmertinger <will...@gmail.com> > wrote: > > You can set user and password with environment variables (PGUSER and > > PGPASSWORD) , also in a Windows batch or program. > > SET PGPASSWORD=xxxyyyzzz > > psql -U "dbadmin" -d mydb -f D:\script.sql > > > > > > > > Regards > > > > Walter > > > > > > On Tue, Jul 27, 2010 at 6:53 PM, <steve.tout...@inspq.qc.ca> wrote: > >> > >> Hi, > >> I created several SQL that are automatically executed via windows task > >> scheduler, here is an example > >> psql -U "dbadmin" -d mydb -f D:\script.sql > >> > >> It was running well until I changed the user (to open a session) > >> associated to these task. > >> The script prompt for a password for user dbadmin. > >> > >> How to avoid that? I guess there is a config so dbadmin will "trust" > this > >> new user.... > >> > >> Thanks for your help, > >> > >> Steve > > > > > > -- > To understand recursion, one must first understand recursion. >
