By default, the Express log in GBase 8a outputs only ERROR and WARN messages — not INFO or DEBUG. This is a deliberate choice that prioritizes production performance while keeping logs readable and manageable.

Primary Reason: Performance First

INFO and DEBUG levels capture extensive execution details — query plan steps, intermediate results, function call stacks. In a high‑concurrency environment, logging all this information generates massive write volumes that drain disk I/O and CPU, directly slowing down query execution. If every SQL statement triggered INFO logging, the log subsystem could become a synchronous bottleneck, inflating response times. Limiting the default to errors and warnings keeps the logging overhead minimal in your gbase database.

Secondary Reason: Readability and Operational Efficiency

Concise logs help DBAs quickly zero in on real issues — failed queries, syntax errors, permission exceptions — without sifting through routine noise.…