Subject | Re: [Firebird-Architect] Re: Group Commits |
---|---|
Author | Jim Starkey |
Post date | 2004-11-08T17:14:33Z |
Dmitry Yemanov wrote:
in the database header and what is managed by configuration file.
In the beginning, there was not configuration file at all, and the
header was the only possible place tuning policy or hints could be
stored. Even in Firebird 2.0, the absence of the ability to specify
parameters on a per-database basis severely limits the usefulness of the
configuration file. But there the Vulcan configuration file system, the
choice is real.
In my mind, stuff stored in the database header page should be limited
to things necessary to read the database -- page size, ods version,
shadow names anem the like. Tuning and operational parameters -- number
of buffers, sweep interval, file open mode, etc. -- should be specified
in the configuration file to allow a dba to experiment with different
settings.
But it isn't feasible at this point for Firebird 2.0 to adopt the Vulcan
configuration file system, so there is no hurry in developing the
guidelines.
[Non-text portions of this message have been removed]
>"Roman Rokytskyy" <rrokytskyy@...> wrote:I think we do need to establish clear guidelines as to what is managed
>
>
>>Will it be possible to update the value with isc_dpb_set_xxx (the same
>>way as, for example, sweep interval is)?
>>
>>
>
>Before answering this concrete question, a general policy should be
>established. See my message "Database-wise settings" in fb-devel.
>
>
>
>
in the database header and what is managed by configuration file.
In the beginning, there was not configuration file at all, and the
header was the only possible place tuning policy or hints could be
stored. Even in Firebird 2.0, the absence of the ability to specify
parameters on a per-database basis severely limits the usefulness of the
configuration file. But there the Vulcan configuration file system, the
choice is real.
In my mind, stuff stored in the database header page should be limited
to things necessary to read the database -- page size, ods version,
shadow names anem the like. Tuning and operational parameters -- number
of buffers, sweep interval, file open mode, etc. -- should be specified
in the configuration file to allow a dba to experiment with different
settings.
But it isn't feasible at this point for Firebird 2.0 to adopt the Vulcan
configuration file system, so there is no hurry in developing the
guidelines.
[Non-text portions of this message have been removed]