Subject | Re[2]: [firebird-support] Re: AGAIN (i know, but different) Max optimized... or not? |
---|---|
Author | Dmitry Kuzmenko |
Post date | 2013-04-16T15:33:08Z |
Hello, fabianoaspro!
Tuesday, April 16, 2013, 5:46:48 PM, you wrote:
fgc> If you use this code inside a SP you must recompile it for using this new
fgc> index.
Just FYI - procedures does not store query plans, so they never need
to be recompiled. Procedure may not use new index because when it
was run, server computed plan, and still use it, while procedure
is being "in use", i.e. in server metadata cache.
When last user who run procedure disconnects, procedure's metatada
being unloaded from cache. And new run will create new plan for this
procedure.
And, doing backup/restore never recompile any procedure/trigger/view.
p.s. All I said is true for all InterBase (from 5.0) versions and for
all Firebird versions.
--
Dmitry Kuzmenko, www.ib-aid.com
Tuesday, April 16, 2013, 5:46:48 PM, you wrote:
fgc> If you use this code inside a SP you must recompile it for using this new
fgc> index.
Just FYI - procedures does not store query plans, so they never need
to be recompiled. Procedure may not use new index because when it
was run, server computed plan, and still use it, while procedure
is being "in use", i.e. in server metadata cache.
When last user who run procedure disconnects, procedure's metatada
being unloaded from cache. And new run will create new plan for this
procedure.
And, doing backup/restore never recompile any procedure/trigger/view.
p.s. All I said is true for all InterBase (from 5.0) versions and for
all Firebird versions.
--
Dmitry Kuzmenko, www.ib-aid.com