You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release adds some bugfixes and optimizations and includes new and refined experimental features.
Experimental Features
Refinements to hyperloglog including a function to report relative error and fixing the functionality of rollup.
Introduction of a TopN approximation API. Presently this will only work for integer data, but expect to see further refinements that greatly expand this behavior.
New map_series and map_data pipeline elements for the time series API that allow uses to provide custom transforms of their time series data. Additionally introduced a |>> pipeline operator for an even more streamlined interface into the new mapping functionality.
Bugfixes/Optimizations
Made a pass through all toolkit functions to correctly label behavior as immutable and parallel safe. This should improve the optimizations Postgres can apply to toolkit plans, particularly when run in a Timescale multinode cluster.
Improved handling of internal data structures to reduce extraneous copies of data.
This discussion was created from the release 1.2.0.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This release adds some bugfixes and optimizations and includes new and refined experimental features.
Experimental Features
hyperloglog
including a function to report relative error and fixing the functionality of rollup.map_series
andmap_data
pipeline elements for the time series API that allow uses to provide custom transforms of their time series data. Additionally introduced a|>>
pipeline operator for an even more streamlined interface into the new mapping functionality.Bugfixes/Optimizations
immutable
andparallel safe
. This should improve the optimizations Postgres can apply to toolkit plans, particularly when run in a Timescale multinode cluster.This discussion was created from the release 1.2.0.
Beta Was this translation helpful? Give feedback.
All reactions