Overhead of turning on debug info

[Carlovski]

I understand that there is an overhead in compiling with debug info turned on?
I have just realised that we have been using PL Developer to compile packages in our production database with the option turned on! (Maybe the default should be that the option is turned off in preferences?)
How significant is the overhead?
Might we have a problem?

 

[Marco Kalter]

The only overhead is in the symbol information added to the compiled object in the dictionary. The actual PL/SQL code is exactly the same, and runs exactly the same. There is only an impact to the object size.

 

[Carlovski]

Phew - There was a post saying this (From another user, not you!)

It used the built in Oracle dbms_debug package (I think thats the one).

It does add overhead, production compiles should be without debug info ALWAYS!

I think that it is REAL BAD to allow debug runs in production (and I am a developer faced with this right now, but I don't think it should be allowed). There should be an almost mirror image of the production DB for trouble shooting and development.

in another thread - got me worried!