* Jeff Davis (pg...@j-davis.com) wrote: > However, the rows will *not* be visible, because the serializable > snapshot doesn't contain the inserting transaction.
That's what we've got now and what would be expected, however...
> Think about the current behavior: right after the commit, another select
> could come along and set all those hint bits anyway. Even if the hint
> bits aren't set, it will do a CLOG lookup and find that the transaction
> committed.
The command is 'FREEZE', which sounded to me like the transaction ID
would be set to FrozenXID, meaning that we wouldn't be able to tell if
the inserting transaction was before or after ours...
Your analysis of the hint bits themselves sounds reasonable but it seems
independent of the issue regarding setting the actual transaction ID.
Thanks,
Stephen
signature.asc
Description: Digital signature
