On Sun, Jul 5, 2015 at 1:19 AM, Fabien COELHO <coe...@cri.ensmp.fr> wrote: > Do you mean I have to proove that there is an actual problem induced from > this patch?
No, I'm not saying anyone *has* to do anything. What I'm saying is that I'm not convinced by your analysis. I don't think we have enough evidence at this point to conclude that a GUC is necessary, and I hope it isn't, because I can't imagine what advice we would be able to give people about how to set it, other than "try all the value and see what works best", which isn't going to be satisfying. More broadly, I don't really know how to test this patch and show when it helps and when it hurts. And I think we need that, rather than just a theoretical analysis, to tune the behavior. Heikki, can you describe what you think a good test setup would be? Like, what workload should we run, and what measurements should we gather to see what the patch is doing that is good or bad? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
