> -----Original Message----- > From: Hogan, James F. Jr. [mailto:[EMAIL PROTECTED] > Sent: 17 January 2006 15:37 > To: Dave Page > Subject: RE: [pgadmin-support] pgagent jobs never start > > Wow that was a world of help adding the -l 2 switch...
Great, glad to hear it's working.) > I will post a Blurb about this to my original post and also submit a > Document update Request to include this "password=" > > Looks like they indented to as I notice that the string example they > provided doesn't have the closing double quote. Not quite :-) The quotes are around the path to the pgAgent executable, not the options. If you read the next section of the docs, you'll see why the password= bit is excluded from the example: Database password - DO NOT be tempted to include a password in the pgAgent connection string - on *nix systems it may be visible to all users in 'ps' output, and on Windows systems it will be stored in the registry in plain text. Instead, use a libpq ~/.pgpass file to store the passwords for every database that pgAgent must access. Details of this technique may be found in the PostgreSQL documentation (http://www.pgadmin.org/docs/1.4/pg/libpq-pgpass.html). (Now available at http://www.pgadmin.org/docs/1.4/pgagent-install.html on the new website that just went live :-) ). The pgpass file should be configured for the Windows user account that the service runs as with appropriate connection info for the databases/postgresql user & password. > Again > > THANK YOU You're welcome. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
