On Thu, Sep 20, 2018 at 10:12:06PM -0700, Andres Freund wrote: > Isn't the point that transaction_timestamp() does *not* currently change > its value, even though the transaction (although not the outermost > statement) has finished?
Ouch, yes. I see the point now. Indeed that's strange to not have a new transaction timestamp after commit within the DO block.. I need a break of a couple of minutes. -- Michael
signature.asc
Description: PGP signature
