Re: ASSM bug: slow INSERT after uncomitted DELETE

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 13 Aug 2009 10:33:49 +0100
Message-ID: <7cudnR7Ij4RnQB7XnZ2dnUVZ8tWdnZ2d_at_bt.com>


"Mladen Gogala" <mladen_at_bogus.email.invalid> wrote in message news:h5vf1r$nnq$2_at_solani.org...
> On Mon, 10 Aug 2009 20:37:35 -0700, Noons wrote:
>
>> Perhaps even more significantly, if you delete only a portion of the
>> table instead of the lot, then the second session's insert is not
>> affected. Normally, I would expect anyone wanting to clear a table to
>> truncate it, as opposed to deleting all rows: truncate is far more
>> efficient.
>
> Unfortunately, in the situations where you want to delete everything
> older than 60 days, truncate is not an option.
>
>
>
> --
> http://mgogala.freehostia.com

It is if you partition by day and use only local indexes ;)

Really, this discussion is only picking up the point that we need to know that each feature has some side effects that may need special consideration.

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
Received on Thu Aug 13 2009 - 04:33:49 CDT

Original text of this message