From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Álvaro Hernández Tortosa <aht(at)nosys(dot)es> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Repeatable read and serializable transactions see data committed after tx start |
Date: | 2015-03-20 20:43:42 |
Message-ID: | 20150320204342.GP6317@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
Attachment | Content-Type | Size |
---|---|---|
mvcc.diff | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-03-20 20:47:49 | Re: proposal: doc: simplify examples of dynamic SQL |
Previous Message | Bruce Momjian | 2015-03-20 20:33:59 | Re: proposal: doc: simplify examples of dynamic SQL |