On 4/16/16 4:44 PM, Noah Misch wrote: > The key judgment to finalize here is whether it's okay to release this feature > given its current effect[1], when enabled, on performance. That is more > controversial than the potential ~2% regression for old_snapshot_threshold=-1. > Alvaro[2] and Robert[3] are okay releasing that way, and Andres[4] is not. If > anyone else wants to weigh in, now is the time.
I'm in favor of releasing the feature even with the performance regression when enabled. First, there are use cases where a feature like this is absolutely critical. Second, I don't think it will improve and become performant without exposure to a wider audience. I think it's entirely within the PostgreSQL philosophy to release a feature that has warts and doesn't perform as well as we'd like as long as it is stable and does not corrupt data. In my opinion this feature meets these criteria and it is an important capability to add to PostgreSQL. -- -David da...@pgmasters.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
