On Fri, Mar 13, 2015 at 8:52 AM, Simon Riggs <[email protected]> wrote: > On 15 February 2015 at 00:19, Kevin Grittner <[email protected]> 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/[email protected] -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
