From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | Raphaël Enrici <blacknoz(at)club-internet(dot)fr> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: CVS Commit by dpage: Use schema 'pgadmin' as PostgreSQL makes it |
Date: | 2005-02-27 19:40:16 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E407B522@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
-----Original Message-----
From: Raphaël Enrici [mailto:blacknoz(at)club-internet(dot)fr]
Sent: Sun 2/27/2005 10:01 AM
To: Dave Page
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [pgadmin-hackers] CVS Commit by dpage: Use schema 'pgadmin' as PostgreSQL makes it
> (thanks for the tip concerning wx2.5.4 DL, the links are up to date now
> on wxwidgets' site.)
np.
> may I ask for a short explanation concerning pgagent? What's the goal of
> this part of the software? What is the schema good for? Storage of data
> used by pgagent? I think I missed a bit of history :).
pgAgent is a maintenance scheduling service/daemon. Andreas wrote most of it some time ago, but then got sidetracked. I'm, err, re-focussing my activities at the moment, and pgAgent seemed like a good way to get back into C++ (I've been doing C# and PHP mainly for the last year or so).
Basically, pgAgent is a bit like the SQL Server Agent in SQL. You can create multi-step jobs (each step is a SQL script, later shell scripts as well), and attach them to a schedule. The service/daemon then runs the steps sequentially at the appropriate time.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-02-27 19:42:38 | new wx lib needed |
Previous Message | cvs | 2005-02-27 13:50:34 | CVS Commit by andreas: 2.5.3 --> 2.5.4 fix paths |