| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce pinning in btree indexes |
| Date: | 2015-03-13 13:17:31 |
| Message-ID: | CA+TgmoZCpGO8MSgQH55LGd5+NUA=sLoDuz29A=qmCe_wirY8xg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 13, 2015 at 8:52 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 15 February 2015 at 00:19, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
>> What they wanted was what happened in the other database product --
>> if a snapshot got sufficiently old that cleaning up the MVCC data
>> was a problem *and* the snapshot was used again *and* it read a
>> page which had been modified far enough back that it was not
>> possible to return correct data, then they wanted to receive a
>> "snapshot too old" error. I wrote a patch to do that...
>
> So, please lets see the patch. It seems useful for core Postgres.
It was submitted here:
http://www.postgresql.org/message-id/136937748.3364317.1423964815320.JavaMail.yahoo@mail.yahoo.com
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-03-13 13:21:46 | Re: CATUPDATE confusion? |
| Previous Message | Robert Haas | 2015-03-13 13:14:19 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |