Re: proposal: contrib module - generic command scheduler

On 5/13/15 1:32 AM, Pavel Stehule wrote:
> 5. When command waits to free worker, write to log
> 6. When command was not be executed due missing workers (and
> max_workers
> > 0), write to log
>
>
> Also unfortunate. We already don't provide enough monitoring
> capability and this just makes that worse.
>
>
> theoretically it can be supported some pg_stat_ view - but I would not
> to implement a some history table for commands. Again it is task for
> higher layers.

I don't think we want to log statements, but we should be able to log
when a job has run and whether it succeeded or not. (log in a table, not
just a logfile).

This isn't something that can be done at higher layers either; only the
scheduler will know if the job failed to even start, or whether it tried
to run the job.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com