Subject | Re: my problem is getting worst |
---|---|
Author | Adam |
Post date | 2008-03-11T23:07:01Z |
--- In firebird-support@yahoogroups.com, "vincent_kwinsey"
<vincent_kwinsey@...> wrote:
message.
Firebird doesn't IMO need journaling (except possibly as a performance
boost) because old record the database file itself is MGA and uses
careful write order. We have hundreds of Firebird databases in all
sorts of environments, and I can count on one hand the number of
corruptions we have had in 4 years. Since I 'had words' with our
implementation team about not file copying databases about 2 years
ago, not one of those corruptions have been on any of our own hosted
servers.
Your prior post indicates to me that you encounter corruptions far
more frequently than me.
Adam
<vincent_kwinsey@...> wrote:
>You seem to have misunderstood my post, or are replying to the wrong
> OK - I will use this as an additional opportunity to ask the DB
> developer team to implement some kind of journaling as a means for
> fast recovery. There is one request for auditing all the SQL
> statmenets in the bug-track, but there should be more heavy emphasis
> on reliability.
message.
Firebird doesn't IMO need journaling (except possibly as a performance
boost) because old record the database file itself is MGA and uses
careful write order. We have hundreds of Firebird databases in all
sorts of environments, and I can count on one hand the number of
corruptions we have had in 4 years. Since I 'had words' with our
implementation team about not file copying databases about 2 years
ago, not one of those corruptions have been on any of our own hosted
servers.
Your prior post indicates to me that you encounter corruptions far
more frequently than me.
Adam