Hi Jan
I have some concerns about wal bloating here.
MarkBufferDirtyHint() forces a WAL record on a dirty page, even for
hints that don't depend on a transaction outcome. The pd_prune_xid
update in heap_page_prune_and_freeze() hits this on every page. With 1M
rows committed before the last checkpoint, the first scan after
promotion wrote 85 MB.
For Zsolt's 2:
xlog_redo() already gets the oldest prepared xid from
PrescanPreparedTransactions()
for a shutdown checkpoint, we can just reuse this?
Thanks,
Shihao