Alphabetical list of options
184
$ For more information, see "TRUNCATE_TIMESTAMP_VALUES
option" on page 215.
DELAYED_COMMITS option
Determines when the server returns control to an application following a
COMMIT.
ON or OFF
Can be set for an individual connection or for the PUBLIC group. Takes
effect immediately.
OFF. This corresponds to ISO COMMIT behavior.
When set to ON, the database server replies to a COMMIT statement
immediately instead of waiting until the transaction log entry for the
COMMIT has been written to disk. When set to OFF, the application must
wait until the COMMIT is written to disk.
When this option is ON, the log is written to disk when the log page is full or
according to the DELAYED_COMMIT_TIMEOUT option setting,
whichever is first. There is a slight chance that a transaction may be lost even
though committed if a system failure occurs after the server replies to a
COMMIT, but before the page is written to disk. Setting
DELAYED_COMMITS to ON, and the DELAYED_COMMIT_TIMEOUT
option to a high value, promotes a quick response time at the cost of security.
If both COOPERATIVE_COMMITS and DELAYED_COMMITS are set to
ON, and if the COOPERATIVE_COMMIT_TIMEOUT interval passes
without the pages getting written, the application is resumed (as if the
commit had worked), and the remaining interval
(DELAYED_COMMIT_TIMEOUT -
COOPERATIVE_COMMIT_TIMEOUT) is used as a
DELAYED_COMMIT interval, after which the pages will be written, even if
they are not full.
DELAYED_COMMIT_TIMEOUT option
Determines when the server returns control to an application following a
COMMIT.
Integer, in milliseconds.
Can be set for an individual connection or for the PUBLIC group. Takes
effect immediately.
Function
Allowed values
Scope
Default
Description
Function
Allowed values
Scope
To Next Page
Loading...