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
When trying to combine data ingested into Postgres through timescaleDB and data in a s3 storage, it is currently slow and cumbersome to load the data from the s3 into postgres.
What does the feature do?
It allows for pg_analytics and timescaledb to coexist in a postgres database, to allow both extensions to work at the same time.
Implementation challenges
Currently, the two extensions clash due to both extensions defining the time_buckets function (paradedb/pg_analytics#150)
The text was updated successfully, but these errors were encountered:
The time_bucket function is the core function that most of the materialized views depends on,
can pg_analytics just skip its own time_bucket function and use the Timescaledb time_bucket function in case the extension already exists?
What problem does the new feature solve?
When trying to combine data ingested into Postgres through timescaleDB and data in a s3 storage, it is currently slow and cumbersome to load the data from the s3 into postgres.
What does the feature do?
It allows for pg_analytics and timescaledb to coexist in a postgres database, to allow both extensions to work at the same time.
Implementation challenges
Currently, the two extensions clash due to both extensions defining the time_buckets function (paradedb/pg_analytics#150)
The text was updated successfully, but these errors were encountered: