Re: Repeatable read and serializable transactions see data committed after tx start - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Repeatable read and serializable transactions see data committed after tx start
Date
Msg-id 20150320204342.GP6317@momjian.us
Whole thread Raw
In response to Re: Repeatable read and serializable transactions see data committed after tx start  (Álvaro Hernández Tortosa <aht@nosys.es>)
Responses Re: Repeatable read and serializable transactions see data committed after tx start
List pgsql-hackers
On Sat, Nov  8, 2014 at 09:53:18PM +0100, Álvaro Hernández Tortosa wrote:
>
> On 07/11/14 22:02, Greg Sabino Mullane wrote:
> >Kevin Grittner wrote:
> >>>I think most people have always assumed that
> >>>BEGIN starts the transaction and that is the point at
> >>>which the snapshot is obtained.
> >>But there is so much evidence to the contrary.  Not only does the
> >>*name* of the command (BEGIN or START) imply a start, but
> >>pg_stat_activity shows the connection "idle in transaction" after
> >>the command (and before a snapshot is acquired)
> >Er...I think we are arguing the same thing here. So no contrary
> >needed? :)
>
>     So do we agree to fix the docs? ^_^

Doc patch attached.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: proposal: doc: simplify examples of dynamic SQL
Next
From: Alvaro Herrera
Date:
Subject: Re: proposal: doc: simplify examples of dynamic SQL