Prevent long transactions when logging smart-large-object data
You can use smart large objects in situations where the
data collection process for a single smart large object lasts for
long periods of time. Consider, for example, an application that records
many hours of low-quality audio information. Although the amount of
data collected might be modest, the recording session might be long,
resulting in a long-transaction condition.
Tip: To prevent
long transactions from occurring, periodically commit writes to smart
large objects.