Effects of the Set Nologging Statement
After the SET NOLOGGING statement is issued, updates performed by the current session are not recorded in the log file or journal files. Updates are not reapplied if the database is rolled forward from a checkpoint, and updates do not appear in an audit trail.
When transaction logging is suspended:
• Any error (including interrupts, deadlock, lock timeout, and force-abort, as well as any attempt to roll back a transaction) results in an inconsistent database. Also, if Ingres or the hardware crashes during the operation, crash recovery will not recover the database, and will mark the database inconsistent.
• The rollforwarddb operation from journals is disabled until the next checkpoint.