Re: Recovery bugs, classified by me

[Philip Stoev]

>> Note that this is just an error printed in the log, the database 
>> continues to run. Therefore "delete all falcon tablespaces" is not a good 
>> workaround because a person may not even notice the problem, since it 
>> does not reveal itself in a crash. God knows what else is also damaged.
>
> Seems to me that if the system tables are not fully established, then the 
> database is not viable and recovery should not be run.

This is fine with me as long as the user is unable to issue any updates 
agains the non-viable database that would be lost when recovery is not run.

The only way I can see to achieve that is to fully establish the system 
tables and make the database viable before the init() function of the Falcon 
plugin returns sucess to the core server and the core server becomes "ready 
for connections".

Philip Stoev