Hi Jey --- Jey Razack <[EMAIL PROTECTED]> wrote: > DB Version : 7.5.00.24 > OS Redhat 2.4.22-1.2199 i686 athlon i386 GNU/Linux > > Immediately after data insert (COMMIT after each > insert), the 'COUNT' function on a table (2.3 > million records) > generates wrong result (higher than the actual). > > Select fld1,count(*) from t1 Where ... group by fld1 > > Re-running the same query after few minutes > generates the correct count. > > We can't reproduce the problem as it occurred > occasionally. > > Is there any way in MAXDB we can force the flush > (dirty data to hard disk) ?. > > Thanks. > Jey Razack
I wonder if this might be related to the problem I encountered a while ago with MaxDB 7.5.0.18. I was getting wrong result from a guery which used aggregate construct sum(distinct abs(<field>)). I have feeling that after some time the query started to work properly, but not 100% sure. I was able to get rid of the problem after I dropped unique index on this table. Hope this helps. Regards. Alexei Novakov -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
