Is it ok to use buffered logging for databases?
On 9th December 2002 mpruet@home.com (Madison Pruet) wrote:- I would not recommend it. We can not replicate the data until the buffer if flushed. If you use buffered logging, then it could be that the commit log record is still in the buffer. That would prevent us from replicating that transaction. Also, in pre 9.3 environments, all of the internal CDR transactions always use unbuffered logging. Therefor, if the user database is buffered and the CDR activity is not, then you will experience a significant increase in log consumption when spooling transactions into the stable queue. This can cause an increase in the probability of getting into a DDRBLOCK state. In 9.3, we are better able to deal with user databases that use buffered logging. But we are still unable to process any transaction until the log buffer containing the commit is flushed. It is necessary to wait until the buffer has been flushed because otherwise, there could be other log records being added to that individual log
