Marko Kreen wrote: > On Mon, Jul 11, 2011 at 5:59 PM, Bruce Momjian <br...@momjian.us> wrote: > > Right now, calling txid_current() causes a session to create a > > non-virtual xid if not already assigned, so observing the xid creates > > it, which seems kind of odd. ?Is that intended? ?Here is the C code: > > Yes, it was intentional, the value will be written out. > > It could be even called before actual writing statement is run > so returning anything that will become invalid later during > transaction is dangerous. > > If you have use-case that requires frequent calling of that function > in read-only transaction, and prefer to see virtual txids > I suggest implementing it as new function.
No, I just considered it strange that it assigned a permenant xid by asking for the value. I have added a C comment documenting this behavior. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
