Mark Dilger <[email protected]> writes:
> Looking closer at the TAP test, it's not ORDERing the result set from the
> SELECTs on either node, but it is comparing the sets for stringwise equality,
> which is certainly order dependent.
Well, it's forcing a bitmap scan, so what we're getting is the native
ordering of a bitmapscan result. That should match, given that what
we're doing is physical replication. I think adding ORDER BY would
be more likely to obscure real issues than hide test instability.
regards, tom lane
