Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Support of pg_analytics #7387

Open
phyk opened this issue Oct 24, 2024 · 2 comments
Open

[Feature]: Support of pg_analytics #7387

phyk opened this issue Oct 24, 2024 · 2 comments
Labels
feature-request Feature proposal

Comments

@phyk
Copy link

phyk commented Oct 24, 2024

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)

@philippemnoel
Copy link

philippemnoel commented Oct 24, 2024

To the Timescale folks -- pg_analytics is now PostgreSQL licensed, so you are free to host it as you wish :)

@jonatas
Copy link

jonatas commented Oct 30, 2024

Thanks for suggesting it @phyk.

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Feature proposal
Projects
None yet
Development

No branches or pull requests

3 participants