Jey Razack 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) ?. Hi Jey, I have some questions about the problem. 1. Is your application single threaded or are multiple session concurrently working on the database? 2. How does the explain output of your statement looks like? 3. How much differ the result? Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
