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

Make telemetry not write to the filesystem #1128

Closed
philippemnoel opened this issue May 13, 2024 · 1 comment
Closed

Make telemetry not write to the filesystem #1128

philippemnoel opened this issue May 13, 2024 · 1 comment
Labels
feature New feature or request pg_lakehouse Issue related to `pg_lakehouse/` pg_search Issue related to `pg_search/` priority-1-high High priority issue quickfix Fast-to-fix issue

Comments

@philippemnoel
Copy link
Collaborator

What
That is a requirement for pg_lakehouse, and we should probably do it for pg_search too, while we're at it. Specifically we need the UUID file to not be written as a file to the filesystem.

Why
This way there truly is no filesystem access need for pg_lakehouse.

How
Write it to a table in the paradedb schema

@philippemnoel philippemnoel added feature New feature or request quickfix Fast-to-fix issue priority-1-high High priority issue pg_search Issue related to `pg_search/` pg_lakehouse Issue related to `pg_lakehouse/` labels May 14, 2024
@neilyio
Copy link
Contributor

neilyio commented Jun 4, 2024

After some investigation, we're going to keep the filesystem approach. Trying to store the UUID in a database is tricky in a bgworker, because we don't really know what database to connect to.

@neilyio neilyio closed this as completed Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request pg_lakehouse Issue related to `pg_lakehouse/` pg_search Issue related to `pg_search/` priority-1-high High priority issue quickfix Fast-to-fix issue
Projects
None yet
Development

No branches or pull requests

2 participants