Re:A Technical Dive into PostgreSQL's replication mechanisms
by jacobprall on Thursday January 11, 2024 @05:09PM
(#38960025)
That's an excellent point. My statement was unnecessarily confusing. I've changed it to simply reference another benefit of the WAL - optimizing I/O operations. That would make a good blog post in and of itself :D
That's not really correct - postgres' MVCC implementation doesn't read from the WAL. Sure, row changes are WAL logged, but that's not really related to MVCC.