| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce pinning in btree indexes |
| Date: | 2015-03-13 12:52:29 |
| Message-ID: | CA+U5nMLPk8xtR3ABebOMu=AW-y0Rgyr6aVv7gHuFeGyocPYTDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-03-13 12:57:44 | Re: Proposal : REINDEX xxx VERBOSE |
| Previous Message | Svenne Krap | 2015-03-13 12:43:26 | Re: WIP Patch for GROUPING SETS phase 1 |