
2-68 IBM Informix OnLine Database Server Administrator’s Guide
Logical Log Buffer
Buffer Contents
Logical log recordsare written continuouslyduring OnLineoperation. Even
if a database is not created with transaction logging, administrative changes
(such as adding a dbspace or a chunk) and data definition statements, such
as CREATE TABLE or DROP TABLE, are logged. (SELECT statements are never
logged.) The logical log files contain five types of records:
■ SQL data definition statements for all databases
■ SQL data manipulation statements for databases that were created
with logging
■ Record of a change to the logging status of a database
■ Record of a checkpoint
■ Record of a change to the configuration
(Refer to page 2-155 for further information about the factors that influence
the number and size of logical log records that are written to the logical log
files.)
Causes of Flushing
Three events cause the logical log buffer to flush:
■ One of the logical log buffers becomes full.
■ A transaction is committed within a database that uses unbuffered
logging.
■ A checkpoint occurs.
Refer to page 2-70 for a definition of a checkpoint. Refer to page 2-72 for a
description of the checkpoint procedure.
If a transaction is committed in a database with unbuffered logging, the
logical log bufferis immediately flushed.Thismight appear tobea source of
some disk space waste. Typically, many logical log records are stored on a
singlepage.Butbecausethelogicallogbufferisflushedinwholepages,even
ifonlyonetransactionrecordisstoredonthepage,thewholepageisflushed.
Intheworstcase, a single COMMIT logicallogrecord(“commitwork”)could
occupyapageondisk,andallremainingspaceonthepagewouldbeunused.
Kommentare zu diesen Handbüchern