|
[
Permalink
| « Hide
]
Dmitry Yemanov added a comment - 05/Jan/09 03:51 AM
The ticket is actually about a few calls (PIO_init_data and PIO_expand) not going through the CCH layer and thus ignoring the backup state.
But is it a really bug\bad behavior ? Database file will grow anyway during the merge... And why it is critical ?
Nobody will be copying the database file during the merge, but this is expected in the stalled state.
Actually, I'm not sure this is really critical. Is a bad file-system level copy of the database possible when the original file is being appended at the end only? But anyway, I think the current design violates the NBACKUP architecture (at least the layering). Nobody but CCH only should be directly calling PIO for write. > Is a bad file-system level copy of the database possible when the original file is being appended at the end only?
I doubt it as file appended with zero's. But i agree that size of file-system level copy would be somewhat bigger than expected ;) > But anyway, I think the current design violates the NBACKUP architecture (at least the layering). Nobody but CCH only should be directly calling PIO for write. Agree, i'll fix it |
|||||||||||||||||||||||||||||||||||||||||||||||||||