On May 4, 2015 02:32:14 PM Yves Dorfsman wrote: > > As for performance concerns, in 99% of cases code maintainability is going > > to be way more important than performance microoptimization. If you're > > *that* concerned about performance than plpgsql probably isn't the right > > answer anyway. > Isn't one of the advantage of running on the server to avoid data round > trip? > > What would you recommend for better performance? You can run python or perl on the server. That's what Jim meant with 'If you're *that* concerned about performance than plpgsql probably isn't the right answer anyway.' Additionally: Many moons ago I did extensive and aggressive performance analysis on a system that did many recursive queries. This was before CTEs (WITH statements) and we settled on recursive plpgsql functions. The queries in the functions were trivial, but nevertheless the bottleneck was in the query and data processing, and never in the surrounding infrastructure. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
