Re: Index-only scans and non-MVCC snapshots

From: Ryan Johnson <ryan(dot)johnson(at)cs(dot)utoronto(dot)ca>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index-only scans and non-MVCC snapshots
Date: 2014-06-27 05:13:52
Message-ID: 53ACFD90.2020806@cs.utoronto.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26/06/2014 11:04 PM, Alvaro Herrera wrote:
> Ryan Johnson wrote:
>> As part of a research project, I'm trying to change Read Committed
>> isolation to use HeapTupleSatisfiesNow rather than acquiring a new
>> snapshot at every command [1].
> Are you aware of this?
>
> commit 813fb0315587d32e3b77af1051a0ef517d187763
> Author: Robert Haas <rhaas(at)postgresql(dot)org>
> Date: Thu Aug 1 10:46:19 2013 -0400
>
> Remove SnapshotNow and HeapTupleSatisfiesNow.
That would be wonderful news... if snapshots weren't so darned expensive
to create.

I guess there's no avoiding that bottleneck now, though.

Ryan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-06-27 05:57:14 Re: WAL replay bugs
Previous Message Alvaro Herrera 2014-06-27 05:04:46 Re: Index-only scans and non-MVCC snapshots