> I think DBA may want a monitoring table (MON$WORKERS?) that shows how
> many workers are currently active, what attachment are they bound to,
> and what task (backup/sweep/etc) are they used for. Maybe some other
> metrics could be added later.
Sounds good to me as well.
--
Mgr. Jiří
16.08.2022 13:02, Jiří Činčura wrote:
Session context variable seems to be a good fit. Monitoring table looks like
overkill.
I think DBA may want a monitoring table (MON$WORKERS?) that shows how
many workers are currently active, what attachment are they bound to,
and what task
Jiří Činčura wrote 16.08.2022 12:02:
Not yet. How would you like to see it ? Monitoring table, session
context variable,
database_info item ? All above ? ;)
Session context variable seems to be a good fit. Monitoring table looks like
overkill. And database_info is inconvenient for end
>Not yet. How would you like to see it ? Monitoring table, session
> context variable,
> database_info item ? All above ? ;)
Session context variable seems to be a good fit. Monitoring table looks like
overkill. And database_info is inconvenient for end users.
> Should user session be
16.08.2022 12:26, Jiří Činčura wrote:
Hi *,
Is there a way to get current value of parallel workers (from i.e. monitoring
tables)?
Not yet. How would you like to see it ? Monitoring table, session context
variable,
database_info item ? All above ? ;) Should user session be allowed to
Hi *,
Is there a way to get current value of parallel workers (from i.e. monitoring
tables)?
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
