| 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:50:57 |
| Message-ID: | 19247.1432662657@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:
> 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.
Well, the patch as proposed failed to do that, but in any case I don't
see much argument for changing the long-established behavior of that
function. Better to add another one if you want a read-only monitoring
probe.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-05-26 17:53:21 | Re: fsync bug faq for publication? |
| Previous Message | Christoph Berg | 2015-05-26 17:47:50 | Re: Why does txid_current() assign new transaction-id? |