Re: why does txid_current() assign new transaction-id? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: why does txid_current() assign new transaction-id?
Date
Msg-id CAHGQGwHPbkyRCTDucTyDjj=AWUYXxTKK4tZog28KdmT5aQ4npw@mail.gmail.com
Whole thread Raw
In response to Re: why does txid_current() assign new transaction-id?  (Naoya Anzai <nao-anzai@xc.jp.nec.com>)
Responses Re: why does txid_current() assign new transaction-id?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Wed, Jun 3, 2015 at 9:04 AM, Naoya Anzai <nao-anzai@xc.jp.nec.com> wrote:
>> > diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
>> > index 89a609f..6485b42 100644
>> > --- a/doc/src/sgml/func.sgml
>> > +++ b/doc/src/sgml/func.sgml
>> > @@ -16233,7 +16233,7 @@ SELECT collation for ('foo' COLLATE "de_DE");
>> >        <row>
>> >         <entry><literal><function>txid_current()</function></literal></entry>
>> >         <entry><type>bigint</type></entry>
>> > -       <entry>get current transaction ID</entry>
>> > +       <entry>get current transaction ID, assigning a new one if current transaction does not have one</entry>
>>                                                                     ^ the
>
> That looks good.

Committed. Thanks!

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: nested loop semijoin estimates
Next
From: Alvaro Herrera
Date:
Subject: Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1