| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: getting rid of SnapshotNow |
| Date: | 2013-07-26 13:01:53 |
| Message-ID: | 20130726130153.GA9000@alap2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-odbc |
On 2013-07-26 08:49:38 -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > OK. I've taken care of all remaining uses of SnapshotNow in the code
> > base. I think we can go ahead and remove it, now. Patch attached.
>
> > (And there was, hopefully, much rejoicing.)
>
> What about SnapshotSelf?
I thought about that yesterday and I think we should replace the usages
which aren't easily replaceable (constraint stuff) with an mvcc
snapshot, just one treats our transaction's current CommandId as
visible. That should be doable?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-07-26 13:03:31 | Re: getting rid of SnapshotNow |
| Previous Message | Robert Haas | 2013-07-26 12:50:51 | Re: dynamic background workers, round two |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-07-26 13:03:31 | Re: getting rid of SnapshotNow |
| Previous Message | Tom Lane | 2013-07-26 12:49:38 | Re: getting rid of SnapshotNow |