Skip site navigation (1) Skip section navigation (2)

Re: Using pgAdmin and pgAgent with Greenplum

From: Dave Page <dpage(at)postgresql(dot)org>
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Using pgAdmin and pgAgent with Greenplum
Date: 2007-10-31 18:49:01
Message-ID: 4728CE1D.6040206@postgresql.org (view raw or flat)
Thread:
Lists: pgadmin-hackers
Roberts, Jon wrote:
>> Roberts, Jon wrote:
>>> There are three problems with having a custom connection string for each
>>> step.  1) If I need to update the connection like change the password, I
>>> have to do it for each step.  2) Developers will see the password in
>> clear
>>> text.
>> I consider those irrelevant because plastered all over the docs will be
>> something like "Don't use passwords here, put them in pgpass files
>> instead". Besides, #2 would be the case even if you defined the servers
>> in a separate table.
>>
> 
> I was unaware of pgpass.  So you are saying I would create/edit the file to
> have hostname:port:database:username:password and then in the step, I would
> just reference the hostname?  If so, I completely agree with you and that
> would be awesome!

You need to specify any non-default values... but then you normally
should be doing that for the pgAgent daemon/service as well (unless you
use ident).

> I'm guessing I can use pgpass with dblink too?

Any libpq based application. It's also where pgAdmin stores passwords
you opt to save.

Regards, Dave

In response to

pgadmin-hackers by date

Next:From: svnDate: 2007-11-01 12:50:44
Subject: SVN Commit by hiroshi: r6805 - trunk/www/download
Previous:From: Roberts, JonDate: 2007-10-31 15:35:16
Subject: Re: Using pgAdmin and pgAgent with Greenplum

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group