Postgres Pro
Downloads
Home   >   mailing lists

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

From Christoph Berg
Subject Re: why does txid_current() assign new transaction-id?
Date
Msg-id 20150530115736.GA17132@msg.df7cb.de
Whole thread Raw
In response to Re: why does txid_current() assign new transaction-id?  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: why does txid_current() assign new transaction-id?  (Naoya Anzai <nao-anzai@xc.jp.nec.com>)
List pgsql-hackers
Tree view 
Re: Michael Paquier 2015-05-28 <CAB7nPqSOx2TEgsypk8gbfa=_hJn7WNLf_tRZexY+SnN3fVF_nA@mail.gmail.com>
> Attached is a doc patch among those lines.

> 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
 

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: initdb -S versus superuser check and Windows restricted mode
Next
From: Bruce Momjian
Date:
Subject: Re: [CORE] postpone next week's release