9653f24ad8
In streaming mode, the transaction can be decoded in multiple streams and those streams can be interleaved with streams of other transactions. So, we can't remember the transaction's write status in the logical decoding context because that might get changed due to some other transactions and lead to wrong answers for 'skip-empty-xacts' option. We decided to keep each transaction's write status in the ReorderBufferTxn to avoid interleaved streams changing the status of some unrelated transactions. Diagnosed-by: Amit Kapila Author: Dilip Kumar Reviewed-by: Amit Kapila Discussion: https://postgr.es/m/CAA4eK1LR7=XNM_TLmpZMFuV8ZQpoxkem--NZJYf8YXmesbvwLA@mail.gmail.com |
||
|---|---|---|
| .. | ||
| concurrent_ddl_dml.spec | ||
| concurrent_stream.spec | ||
| delayed_startup.spec | ||
| mxact.spec | ||
| oldest_xmin.spec | ||
| ondisk_startup.spec | ||
| snapshot_transfer.spec | ||
| subxact_without_top.spec | ||