On 2020-Mar-27, Tom Lane wrote: > That being the case, I'd think a better design principle is "make your > new code look like the code around it", which would tend to weigh against > introducing StringInfo uses into pgbench when there's none there now and > a bunch of PQExpBuffer instead. So I can't help thinking the advice > you're being given here is suspect.
+1 for keeping it PQExpBuffer-only, until such a time when you need a StringInfo feature that's not in PQExpBuffer -- and even at that point, I think you'd switch just that one thing to StringInfo, not the whole program. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
