I can see that and considered it.
The seed state would need to be saved, or any particular command that is
not reproducible would need to be exempted from this sort of logging.
Again, this would apply only to situations where a small SQL command
created huge changes.
Marty
Rod Taylor wrote:
>>If a transaction will do large updates or inserts, why don't we just log
>>the parsed statements in the WAL instead of the individual data blocks
>
>
> UPDATE table SET col = random();
>
>