| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Ryan Johnson <ryan(dot)johnson(at)cs(dot)utoronto(dot)ca> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Index-only scans and non-MVCC snapshots |
| Date: | 2014-06-27 05:04:46 |
| Message-ID: | 20140627050445.GK7340@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
We now use MVCC catalog scans, and, per discussion, have eliminated
all other remaining uses of SnapshotNow, so that we can now get rid of
it. This will break third-party code which is still using it, which
is intentional, as we want such code to be updated to do things the
new way.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Johnson | 2014-06-27 05:13:52 | Re: Index-only scans and non-MVCC snapshots |
| Previous Message | Ryan Johnson | 2014-06-27 04:47:47 | Index-only scans and non-MVCC snapshots |