Subject Re: Something IS seriously broken between 2.1.3 and 2.1.4
Author chris.waldmann
Hello William

> > What is plan produced in 2.1.3 and 2.1.4
> > if you can not get detailed plan when do
> > select * from schedule_getclientlist('19', -1, 'Y', 'N');
> >
> > then try change this proc to execute block and get detailed plan
> > and we will see where is different
> >
> > Karol Bieniaszewski
> >
> >
>
> OK. I changed the stored procedure a bit so now I can see the plans. the
> only different:
>
> under 2.1.3, Indexes used for INCIDENT: only IDX_INCIDENT_CLIENTID
>
> under 2.1.4, Indexes used for INCIDENT: IDX_INCIDENT_CLIENTID and
> IDX_INCIDENT_DISCHARGEDATE.
>
>
> William
>
>
May be you have to adapt the firebird.conf to keep the pages for both indexes in RAM. My settings for a Super Server 2.1.x are:

DefaultDbCachePages = 65536
MaxFileSystemCache = 0

Good luck
Christian