Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: why does txid_current() assign new transaction-id?
Date
Msg-id CAB7nPqTxrunRMez-HauhrH_k_B6ir+UgzvS+MRxWg3MnHGsazA@mail.gmail.com
Whole thread Raw
In response to Re: why does txid_current() assign new transaction-id?  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Tree view


On Wed, Jun 3, 2015 at 12:13 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
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!
 
Thanks for picking up the fix.
--
Michael

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: auto_explain sample rate
Next
From: Andres Freund
Date:
Subject: Re: auto_explain sample rate