Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Bug Description
fix issues found by Coverity Scan in taosdump.c

To Reproduce
Steps to reproduce the behavior:
N/A

Expected Behavior
fix following issues found by Coverity Scan in taosdump.c

1. String not null terminated High TDengine/src/kit/taos-tools/src/benchUtil.c postProceSql
2. Resource leak High TDengine/src/kit/taos-tools/src/taosdump.c parse_json_to_recordschema
   3

Relevant telegraf.conf:

[[inputs.openweathermap]]
  app_id = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
  

Scenario

A user is ingesting some data (~300M rows) into a table with 270K distinct symbol values. For each of these 270K symbols we end up with at least one posix_fallocate() necessary to add a new value block. See the below flamegraph - it's quite illustrative.

An important part of the scenario is non-default index block capacity which is set to 2048. With the default capacity (w