Subject | Re: [Firebird-Architect] Read Committed No Wait transactions |
---|---|
Author | Ann W. Harrison |
Post date | 2004-09-23T18:20:21Z |
At 03:00 PM 9/22/2004, Ivan Prenosil wrote:
combined with no_wait. Looking back over the archive, the combination
of options Nickolay used seems to be read_committed, no_record_versions,
and wait, which is a vaguely plausible combination. The application
was based on a load test adapted from Oracle.
Regards,
Ann
>I do not remember exact details, but Nickolay used no_record_versionsThere's nothing (much)wrong with no_record_versions until it's
>to solve some problems in heavy contention environment
>(basically, without it nobody was able to do any useful work
>because of constant lock conflicts/deadlocks)
combined with no_wait. Looking back over the archive, the combination
of options Nickolay used seems to be read_committed, no_record_versions,
and wait, which is a vaguely plausible combination. The application
was based on a load test adapted from Oracle.
Regards,
Ann