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

From Jim Nasby
Subject Re: Repeatable read and serializable transactions see data committed after tx start
Date
Msg-id 545A544F.2030406@BlueTreble.com
Whole thread Raw
In response to Re: Repeatable read and serializable transactions see data committed after tx start  (Álvaro Hernández Tortosa <aht@8Kdata.com>)
Responses Re: Repeatable read and serializable transactions see data committed after tx start  (Kevin Grittner <kgrittn@ymail.com>)
Re: Repeatable read and serializable transactions see data committed after tx start  (Álvaro Hernández Tortosa <aht@8Kdata.com>)
List 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'sdriven 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: tracking commit timestamps
Next
From: Andrew Dunstan
Date:
Subject: Re: get_cast_func syscache utility function