On 13 March 2015 at 13:17, Robert Haas <robertmh...@gmail.com> wrote: > On Fri, Mar 13, 2015 at 8:52 AM, Simon Riggs <si...@2ndquadrant.com> wrote: >> On 15 February 2015 at 00:19, Kevin Grittner <kgri...@ymail.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.ya...@mail.yahoo.com
Thanks. I have +1'd that patch. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
