Re: SQL performance in prod

From: Andy Sayer <andysayer_at_gmail.com>
Date: Thu, 26 Jul 2018 08:28:21 +0100
Message-ID: <CACj1VR45ub6WX6fnZUbgFX-TdK2jgup76rxQgyKR6AHQbGFtTw_at_mail.gmail.com>



Mladen,

“My assumption was that the plans for a single execution are different. I maybe wrong.”

I was referring to the execution of a single line in the plan. eg for a nested loop: there will be multiple executions of the plan lines that hit the joined table (assuming multiple rows in the driving table), the e-rows represents the number of rows the CBO expects to find on one iteration.

Assuming one statement execution. A-rows will be the total number of rows flowing from that row source from the entire execution of the statement. So you would have to multiply the E-rows by the number of times the line was hit

Hopefully that’s clearer now

Andy

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jul 26 2018 - 09:28:21 CEST

Original text of this message