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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: Naoya Anzai <nao-anzai(at)xc(dot)jp(dot)nec(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com>
Subject: Re: Why does txid_current() assign new transaction-id?
Date: 2015-05-26 17:38:25
Message-ID: 18863.1432661905@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christoph Berg <myon(at)debian(dot)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(). In either case it would have to be a new function,
not unilaterally redefining what txid_current() does.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2015-05-26 17:47:50 Re: Why does txid_current() assign new transaction-id?
Previous Message Christoph Berg 2015-05-26 17:27:14 Re: Why does txid_current() assign new transaction-id?