Tom Lane wrote:
Stefan Kaltenbrunner <ste...@kaltenbrunner.cc> writes:
hmm I tend to disagree, this patch was specifically done to address a
hotspot I noticed under a given workload and it helped a lot for that
workload(like getting 6000qps more is pretty neat imho).
While people might not use fixed width chars that often(which especially
for migrated database is imho not true) it is an issue that can be seen
with a rather popular database related benchmarking tool so we should
not really dismiss it easily.
Nobody suggested dismissing it. The point was that it hasn't been
tested adequately to justify applying it now.
not sure what testing people want to get done though (there are a fair
amount of results and profiles in the thread)?
Stefan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
