SEO

#1 (**permalink**) 04-18-2008, 08:53 AM

>
> > However, to make pgAgent and pgAdmin work better with my solution, it
> would
> > be nice to have an enhancement. The enhancement could also benefit
> others
> > wanting to separate the database server where jobs are maintained from
> the
> > target server(s) where sql should be executed.
> >
> > On the screen where you define a SQL step, add another parameter for
> Server.
> > When executing the SQL defined, pgAgent would connect to the Server and
> then
> > execute the SQL defined in the database specified in the step.
> >
> > This solution would require an additional screen to define the servers
> too.
> >
> > Is there much demand for allowing a SQL job step to be executed on a
> remote
> > server and database?
>
> I've never heard anyone ask before, but I don't think it's an
> unreasonable request. It would be more simple to just add an additional
> textbox to the SQL Step to allow a custom connection string to be
> specified. If blank it works as now, otherwise it just uses whats there.
>
> Anyone wanna pickup this mod?
>
> /D

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. 3) It is error prone because I might mistype the connection
information for a step.

I am glad that you are interested in adding this mod and I'm glad that
PostgreSQL works so well for this.

Jon

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#2 (**permalink**) 04-18-2008, 08:53 AM

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.

> 3) It is error prone because I might mistype the connection
> information for a step.

Copy 'n' paste is your friend :-). But yes, that could be an issue. Not
sure if it's worth the hassle of a whole extra UI for maintaining server
definitions though - I'd guess not to be honest.

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: Using pgAdmin and pgAgent with Greenplum