Subject | Re: [firebird-support] Effect of DefaultDbCachePages? |
---|---|
Author | Alexandre Benson Smith |
Post date | 2009-01-21T15:46:45Z |
Hi Ivan,
Ivan Prenosil wrote:
cache, In my mind the precedence would be:
1) if you specified cache size during connection, that value is used. Period
otherwise
2) if the database has specified cache size (e.g. using gfix), then that
value is used
otherwise
3) DefaultDbCachePages is used.
In fact it doesn't matter in practice for me I never use connection
specific buffer size, just the database specified one. But I think the
order I said would make more sense (at least on my narrow point of
view), since if I want for some reason and for a special case a distinct
buffer size I could supply it just for that connection, overriding the
database default.
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
Ivan Prenosil wrote:
> 1) if the database has specified cache size (e.g. using gfix), then that value is used. Period.I though that the connection parameter would override the database page
> otherwise
> 2) if you specified cache size during connection, that value is used,
> otherwise
> 3) DefaultDbCachePages is used.
>
cache, In my mind the precedence would be:
1) if you specified cache size during connection, that value is used. Period
otherwise
2) if the database has specified cache size (e.g. using gfix), then that
value is used
otherwise
3) DefaultDbCachePages is used.
In fact it doesn't matter in practice for me I never use connection
specific buffer size, just the database specified one. But I think the
order I said would make more sense (at least on my narrow point of
view), since if I want for some reason and for a special case a distinct
buffer size I could supply it just for that connection, overriding the
database default.
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br