Subject | Re: [firebird-support] Why write async is bad ? |
---|---|
Author | Vander Clock Stephane |
Post date | 2012-01-11T05:43:57Z |
ok thanks ann, i understand now why the write are done inside a
connection thread ...
connection thread ...
On 1/11/2012 1:08 AM, Ann Harrison wrote:
>
> Stepane,
>
> >
> > when i setup write async to true, it's mean the the database will store
> > in memory the write and after several update (5 by default?) all the
> write will be flush to
> > the disk.
>
> Firebird's internal consistency depends on "careful write" - Firebird
> writes database pages in a specific order to avoid dangling pointers.
> Asynchronous writes are done in the order that the operating system
> finds convenient. That is not a good idea. If you have a system
> crash, the database on disk is likely to be corrupt and difficult, if
> not impossible to recover.
> >
> > The main drawback, is that all the write are flush to the disk using the
> > current connection thread :(
>
> No, I wouldn't consider that the main drawback. Potentially
> irrecoverable corruption is a pretty serious drawback.
>
> > i was thinking that it's a separate thread that was responsible to flush
> > to disk :( or i m wrong?
>
> Is it wrong to live dangerously? Maybe so, maybe not.
>
> Good luck,
>
> Ann
>
>
[Non-text portions of this message have been removed]