3 ms·

It's unclear - What is this supposed to be better than, and what about it is supposed to better?

Illniyar 10y ago
It seems to me it's extremely clear from the first paragraph - it's supposed to be better the pgagent, and the second paragraph lists all the new features that make it better then pgagent.
- RangerScience 10y ago
  It's unclear because the second paragraph is about why the replacement is compatible with pgAgent, literally, "The reason for..." - not that it is a replacement. It could also be a replacement for something else that runs on top of pgAgent, or something else that doesn't, and one of the features is that this is compatible. Does that make sense?
Tostino 10y ago
Right in the second paragraph: > The reason for writing a pgAgent compatible job scheduler is to be able to utilize the tools already in place for pgAgent in the pgAdmin UI, minimizing the pain of switching for existing pgAgent users (uses the same database schema), and provide a more stable and feature rich implementation of the agent. So pgAgent: https://www.pgadmin.org/docs/dev/pgagent.html https://www.pgadmin.org/docs/dev/pgagent.html is what it's supposed to be better than, but also compatible with. It uses the pgAgent database schema, and UI built into pgAdminIII/4. Now how it's better...good point. Not very obvious to someone who isn't familiar with pgAgent already. Everything listed under Additional Features is something which is available with jpgAgent and is not available in regular pgAgent. So a quick list of additional features: 1. Job / job step timeouts (fail a job if it's taken longer than x time) 2. Email notifications on jobs and job steps which can notify you of the status 3. Optionally run job steps in parallel. 4. Manually kill a specific job (there is no way to do that in pgAgent) 5. Good logging (as opposed to almost non-existent logging). 6. Is an actual stable agent. It won't crash on you without warning and leave you wondering why your jobs suddenly stopped running.
davidbanham 10y ago
I guess it's supposed to be better than pgagent. Whatever that is.
- Tostino 10y ago
  It's an in-database cron pretty much... info here if you're interested: https://www.pgadmin.org/docs/dev/pgagent.html https://www.pgadmin.org/docs/dev/pgagent.html

It seems to me it's extremely clear from the first paragraph - it's supposed to be better the pgagent, and the second paragraph lists all the new features that make it better then pgagent.

RangerScience 10y ago
It's unclear because the second paragraph is about why the replacement is compatible with pgAgent, literally, "The reason for..." - not that it is a replacement. It could also be a replacement for something else that runs on top of pgAgent, or something else that doesn't, and one of the features is that this is compatible. Does that make sense?

Tostino 10y ago

Right in the second paragraph: > The reason for writing a pgAgent compatible job scheduler is to be able to utilize the tools already in place for pgAgent in the pgAdmin UI, minimizing the pain of switching for existing pgAgent users (uses the same database schema), and provide a more stable and feature rich implementation of the agent. So pgAgent: https://www.pgadmin.org/docs/dev/pgagent.html https://www.pgadmin.org/docs/dev/pgagent.html is what it's supposed to be better than, but also compatible with. It uses the pgAgent database schema, and UI built into pgAdminIII/4. Now how it's better...good point. Not very obvious to someone who isn't familiar with pgAgent already. Everything listed under Additional Features is something which is available with jpgAgent and is not available in regular pgAgent. So a quick list of additional features: 1. Job / job step timeouts (fail a job if it's taken longer than x time) 2. Email notifications on jobs and job steps which can notify you of the status 3. Optionally run job steps in parallel. 4. Manually kill a specific job (there is no way to do that in pgAgent) 5. Good logging (as opposed to almost non-existent logging). 6. Is an actual stable agent. It won't crash on you without warning and leave you wondering why your jobs suddenly stopped running.

davidbanham 10y ago

I guess it's supposed to be better than pgagent. Whatever that is.

Tostino 10y ago
It's an in-database cron pretty much... info here if you're interested: https://www.pgadmin.org/docs/dev/pgagent.html https://www.pgadmin.org/docs/dev/pgagent.html