Thomas Munro <thomas.mu...@gmail.com> writes:
> On Fri, Mar 5, 2021 at 5:10 PM Tom Lane <t...@sss.pgh.pa.us> wrote:
>> Alternatively, maybe we can salvage the function's usefulness by making it
>> flush WAL before returning?
> To make pg_xact_status()'s result reliable, don't you need to make
> pg_current_xact_id() flush? In other words, isn't it at the point
> that you *observe* the transaction that you have to make sure that
> this transaction ID won't be reused after crash recovery. Before
> that, it's simultaneously allocated and unallocated, like the cat.
We need to be sure that the XID is written out to WAL before we
let the client see it, yeah. I've not looked to see exactly
where in the code would be the best place.
BTW, I tried simply removing the "allows_streaming" option from
the test, and it failed ten times out of ten tries for me.
So Andres is right that that makes it pretty reproducible in
a stock build.
regards, tom lane
