> > But one of the purposes of pgbench is examining performance on > > different environments, doesn't it? I'm afraid hard coded > > PREPARE/EXECUTE makes it harder. > > I was just thinking that pgbench is for measuring code changes, not for > testing changes _in_ pgbench. Once we know the performance difference > for PERFORM, would we still keep the code in pgbench? Maybe to test > later, I guess.
My concern is PREPARE/EXECUTE may NOT always improve the performance. I guess we have very few data to judge PREPARE/EXECUTE is good or not. Moreover PREPARE/EXECUTE might be improved in the future. If that happens, keeping that switch would help examining the effect, no? -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
