On Fri, Oct 13, 2017 at 1:59 PM, Peter Geoghegan <p...@bowt.ie> wrote: >> Fully agreed. > > If we implement that interface, where does that leave EvalPlanQual()? > Do those semantics have to be preserved?
For a general-purpose heap storage format, I would say yes. I mean, we don't really have control over how people use the API. If somebody decides to implement a storage API that breaks EvalPlanQual semantics horribly, I can't stop them, and I don't want to stop them. Open source FTW. But I don't really want that code in our tree, either. I think a storage engine is and should be about the format in which data gets stored on disk, and that it should only affect the performance of queries not the answers that they give. I am sure there will be cases where, for reasons of implementation complexity, that turns out not to be true, but I think in general we should try to avoid it as much as we can. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers