Releases: nickbabcock/pg-collectd
Releases · nickbabcock/pg-collectd
v0.2.0 - April 26th, 2020
Another maintenance release but contains updates to bigger internal dependencies. If compiling pg-collectd from source and using the collectd version autodetection, pg-collectd now supports collectd 5.9 - 5.11.
v0.1.5 - October 10th, 2019
- Maintenance release that bumped internal dependencies
v0.1.4 - February 6th, 2019
- Bump collectd-plugin from 0.9.0 to 0.9.1
- Compile on non-x86 platforms
- Add
COLLECTD_PATH
environment variable for detecting collectd version from collectd's source directory (most useful with thebindgen
feature). - Output panic info into collectd logs
v0.1.3 - January 16th, 2019
Extremely minor release -- basically ensuring that the automated CI deployments worked
Internal dependency updates:
- Update csv from 1.0.2 to 1.0.5
- Update serde / serde_derive from 1.0.82 to 1.0.84
- Update parking_lot from 0.7.0 to 0.7.1
- Update failure from 0.1.3 to 0.1.5
v0.1.2 - December 16th, 2018
- Reduce memory allocations necessary after a failure inserting into the database
- If there was a db failure and we're trying to insert again within the same second -- give the db a break and discard those values
- Bumping the internal collectd plugin to 0.9 from 0.8.4 improves resiliancy that unexpected panics won't bring collectd down
v0.1.1 - Nobember 26th, 2018
- Update to collectd-plugin 0.8.4 from 0.8.1, which fixes segfaults on plugin flush and shutdown
- Add: configurable log level for timing data using the LogTimings configuration option (an example of a log timing: "inserted 1000 rows from 1000 values from 86403 bytes (capacity: 157696) in 54ms")
- Fix batch limit logic so that if it is reached (and not only when it is exceeded)
pg-collectd
will submit values to Postgres. Previously if one had a batch limit of10
, those 10 values wouldn't be submitted until the 11th value was received. Very minor logic change from> self.batch_limit
to>= self.batch_limit
.
v0.1.0 - October 31st, 2018
Initial release