Subject | Re: Webserver crash due to Ibase problems |
---|---|
Author | Mikael Krogius |
Post date | 2005-11-08T16:08:59Z |
Thanks Lester,
1.5 (a year ago or so) etc, but as some of these earlier versions
caused problems and didn't want to pay the Interbase fees so we ended
up running it on FB2.
ibase_prepare() + _execute(). It seems that using transactions is more
stable, and it also reveals some deadlocks that was not visible
without transactions. But nevertheless, it still keeps going haywire.
lower value at some point. I think I better try to recreate the tables
with FB1.5 and Pump the data into those tables.
I'll post if I get it working, in the meantime more suggestions are
welcome :)
Cheers,
Mikael
> Well starting with a pre-production copy of Firebird wasOver time it has been running on Interbase 6, 7, 7,1, 7.5 and Firebird
> probably not a good idea, back porting the data will be
1.5 (a year ago or so) etc, but as some of these earlier versions
caused problems and didn't want to pay the Interbase fees so we ended
up running it on FB2.
> Try starting your own transaction after starting theI have tried both using a transaction with ibase_query() and with
> connection and close it at the end. The default stuff
> seems a little less than robust, and you can set your
> own settings.
ibase_prepare() + _execute(). It seems that using transactions is more
stable, and it also reveals some deadlocks that was not visible
without transactions. But nevertheless, it still keeps going haywire.
> Also - have you disabled sweep - not sure on FB2, butNo, I have not tried disabling sweep. In fact, I set the sweep to a
> on FB1.5 running that 'out of hours' prevents it kicking
> off just when a big update startes ;)
lower value at some point. I think I better try to recreate the tables
with FB1.5 and Pump the data into those tables.
I'll post if I get it working, in the meantime more suggestions are
welcome :)
Cheers,
Mikael