Path: text.usenetserver.com!out02a.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!34g2000hsz.googlegroups.com!not-for-mail
From: Mark D Powell <Mark.Powell@eds.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: why does 11g plsql_code_type default to interpreted?
Date: Mon, 3 Mar 2008 07:41:21 -0800 (PST)
Organization: http://groups.google.com
Lines: 29
Message-ID: <96bdf326-db77-4bc9-8115-ed995e8595d6@34g2000hsz.googlegroups.com>
References: <8e57c34f-c983-461e-8de0-6c78f2cf1926@u69g2000hse.googlegroups.com>
NNTP-Posting-Host: 192.85.50.12
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1204558882 26104 127.0.0.1 (3 Mar 2008 15:41:22 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 3 Mar 2008 15:41:22 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: 34g2000hsz.googlegroups.com; posting-host=192.85.50.12; 
 posting-account=qJFqbQkAAACYQSLN0-cvP6ydkRfuOu6u
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET 
 CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
Xref: usenetserver.com comp.databases.oracle.server:442055
X-Received-Date: Mon, 03 Mar 2008 10:41:22 EST (text.usenetserver.com)

On Mar 3, 9:46=A0am, hpuxrac <johnbhur...@sbcglobal.net> wrote:
> I have a test system running 11g 64 bit on OEL 4. =A0Created a new
> database ( custom ... not from template with pre-suppplied
> datafiles ).
>
> It seems kind of curious that oracle is defaulting plsql_code_type to
> interpreted.
>
> If the native is so much faster ... and you don't need a compiler/etc
> anymore ... why is this happening for a new database?
>
> Are there a bunch of bugs and caveats that are still being experienced
> in this area? =A0Maybe this default will eventually change by 11.2?

Think back to the java verse PL/SQL discussions.  I think the issues
are the same.

My guess as to why PL/SQL defaults to interpreted execution is becuase
first this is how the code ran in the past and second in most cases
the interpreted code is just as fast as compiled code.  Compiled code
really only has an advantage when most of the time is not spent in SQL
calls, which are passed to the SQL engine.  Most existing PL/SQL is
not calculation intensive and spends most of its time performing SQL
calls.

IMHO -- Mark D Powell --



