Re: Repeatable read and serializable transactions see data committed after tx start

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Álvaro Hernández Tortosa <aht(at)8Kdata(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Repeatable read and serializable transactions see data committed after tx start
Date: 2014-11-05 16:46:07
Message-ID: 545A544F.2030406@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/4/14, 6:11 PM, Álvaro Hernández Tortosa wrote:
> Should we improve then the docs stating this more clearly? Any objection to do this?

If we go that route we should also mention that now() will no longer be doing what you probably hope it would (AFAIK it's driven by BEGIN and not the first snapshot).

Perhaps we should change how now() works, but I'm worried about what that might do to existing applications...
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-11-05 16:48:43 Re: get_cast_func syscache utility function
Previous Message Andres Freund 2014-11-05 16:38:14 Re: tracking commit timestamps