Subject | Re: AW: [firebird-support] How to test for forced writes? |
---|---|
Author | Ann W. Harrison |
Post date | 2011-01-26T22:42:17Z |
On 1/26/2011 5:31 PM, Steffen Heil wrote:
header page. If there's no indication of the state, then forced
writes are on, which is the default. When nothing shows up in
gstat, it's because there are no entries for write status in
the variable portion of the header.
If forced writes are off, gstat will show that, every time.
is created when the state is changed from the default, and replaced when
changed back.
Good luck,
Ann
>The status of forced writes is in the variable portion of the
> Yet, what makes me headaches is, that gstat will only the the forces writes
> status, if it was ealier set using gfix. This looks like gfix is adding
> something that gstat will show besides really switching on forced writes.
header page. If there's no indication of the state, then forced
writes are on, which is the default. When nothing shows up in
gstat, it's because there are no entries for write status in
the variable portion of the header.
If forced writes are off, gstat will show that, every time.
> Which once again might mean, that it could be possible that the real forcedBy default, there is no forced write flag. An entry for forced writes
> write flag is modified without modifying the header that gstat shows,
> leading to a situation where gstat reports forced writes while it is not
> really in effect...
is created when the state is changed from the default, and replaced when
changed back.
Good luck,
Ann