Confusion about In-Memory logging and Permanent message

Question

Dear sir:
In the Replication C-GSG.pdf document, it describes as follow:
For the master (again, using the replication framework), things are a little more
complicated than simple message acknowledgment. Usually in a replicated application,
the master commits transactions asynchronously; that is, the commit operation does not
block waiting for log data to be flushed to disk before returning. So when a master is
managing permanent messages, it typically blocks the committing thread immediately
before commit() returns. The thread then waits for acknowledgments from its replicas.
If it receives enough acknowledgments, it continues to operate as normal.
If the master does not receive message acknowledgments — or, more likely, it does not
receive enough acknowledgments — the committing thread flushes its log data to disk
and then continues operations as normal. The master application can do this because
replicas that fail to handle a message, for whatever reason, will eventually catch up to
the master. So by flushing the transaction logs to disk, the master is ensuring that the
data modifications have made it to stable storage in one location (its own hard drive).
My question:
If I have configured IN-Memory Logging in the logging subsystem, is it means that even the master does not receive enough acknowledgments, the committing thread will not flush the log data to disk and just let it stay in the memory region?

Answer 1

Yes, that's correct.
You might find this additional information helpful:
db-4.5.20/docs/ref/program/ram.html