I agree with Tom's reasoning about the suggested simplifications, sorry.
> > 3. Should the WALWriter also do the wal_buffers half-full write at
the
> > start of XLogInsert() ?
>
> That should go away entirely; to me the main point of the
> separate wal-writer process is to take over responsibi
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> transaction_guarantee.v11.patch
I can't help feeling that this is enormously overcomplicated.
The "DFC" in particular seems to not be worth its overhead. Why wouldn't
we simply track the newest commit record at all times, and then whenever
the wal wri
