Reading my own words, I think I must fix an ambiguity: On Fri, Jul 10, 2020 at 3:23 PM Amit Langote <amitlangot...@gmail.com> wrote: > So even if an AM's table_tuple_insert() itself doesn't populate the > transaction info into the slot handed to it, maybe as an optimization, > it does not sound entirely unreasonable to expect that the AM's > slot_getsysattr() callback returns it correctly when projecting a > target list containing system columns.
The "maybe as an optimization" refers to the part of the sentence that comes before it. That is, I mean table_tuple_insert() may choose to not populate the transaction info in the slot as an optimization. -- Amit Langote EnterpriseDB: http://www.enterprisedb.com
