Re: Why does txid_current() assign new transaction-id?

Re: Tom Lane 2015-05-26 <18863.1432661905@sss.pgh.pa.us>
> Christoph Berg <myon@debian.org> writes:
> > Still, exposing GetStableLatestTransactionId() on the SQL level would
> > make sense for monitoring transaction throughput.
> 
> Perhaps, though I wonder why we should expose that and not just report the
> result of ReadNewTransactionId() --- or in txid.c's case, the result of
> GetNextXidAndEpoch().

Whatever is most suitable, yes.

> In either case it would have to be a new function,
> not unilaterally redefining what txid_current() does.

Sure.

I think the OP's point was (or should have been), to make txid_current
not draw a new xid when run outside a transaction block, though it's
questionable if that wouldn't just add a POLA-violating layer.

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/