> I'll try to look into that with lower page sizes for relation and WAL pages.
The page size is totally unrelated to this bug. When you repro the redo failure it is because the log record is being applied to an old page version. The correct newer page version never got written because of the truncate page invalidation. The cause is not a torn write.
> What's that?
Azure PostgreSQL on Windows has proprietary mechanisms in its filesystem to guarantee that a write is atomic.
- Dan
On Thu, Nov 14, 2019 at 07:38:19PM -0800, Daniel Wood wrote:
Sorry I missed one thing. Turn off full page writes.
Hmm. Linux FSes use typically 4kB pages. I'll try to look into that
with lower page sizes for relation and WAL pages.
I'm running in an env. with atomic 8K writes.
What's that?
--
Michael
