Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verbose mode for gfix [CORE2667] #3071

Open
firebird-automations opened this issue Oct 6, 2009 · 2 comments
Open

Verbose mode for gfix [CORE2667] #3071

firebird-automations opened this issue Oct 6, 2009 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @WarmBooter

When gfix is running in big/corrupted databases, it would be good to "see" something happening to be sure that it is actually "doing" something, and not got stuck at some phase, or just entered an infinite loop (due to corruption).

As the possibility of adding progress bars, etc seems to be improbably, some basic information would help, ie:

Object name being analyzed
Incremental number of pages accessed for that object
Starting Time for that object (end time when job finishes)
Maybe some alert if a specific page was read more than 100 times (possible infinite loop detected)

Anyway, anything more than a black "silent" screen would be welcome. Maybe the same info can be shown when sweep is being done.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

This requires relatively serious changes in engine and (sooner of all) public API. The reason for it is that gfix utility itself does almost nothing - it converts switches to appropriate DPB parameters, and teh rest of the job is done by engine, at server side. May be technique, similiar to one used by monitoring tabkes can be used here... This should be carefully thought before doing something, therefore I do not assigned planned version to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants