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

pg_stat_progress_create_index doesn't report index creation on hypertable #3157

Open
maltalex opened this issue Apr 25, 2021 · 3 comments
Open
Labels

Comments

@maltalex
Copy link

Relevant system information:

  • OS: Ubuntu 20.04
  • PostgreSQL version (output of postgres --version): 13.2
  • TimescaleDB version (output of \dx in psql): 2.2.0
  • Installation method: Official Docker image - timescale/timescaledb:2.2.0-pg13

Describe the bug
According to the pg 13 documentation, pg_stat_progress_create_index should show index creation progress. However, index creation on hypertables doesn't seem to show up.

I've been creating an index on a large dataset for several hours now and select query from pg_stat_activity; shows several worker threads executing a CREATE INDEX on the hypertable, but pg_stat_progress_create_index doens't show anything.
In case it's relevant, I'll mention that the hypertable has compression enabled, and the index is being built on the segment-by columns.

Expected behavior
Progress towards index creation should show up in pg_stat_progress_create_index

@mkindahl
Copy link
Contributor

@maltalex Thank you for a very interesting feature request. Not sure how easy it is to implement, but we will investigate.

@maltalex
Copy link
Author

maltalex commented May 2, 2021

@mkindahl
Is there a list somewhere of postgres features that aren't supposed to work on hypertables? It's sometimes hard to tell the difference between features and bugs when some standard postgres thing doesn't work as expected on a hypertable.

I would be nice to have a list of known places where the hypertable abstraction is leaking.

@RobertAron
Copy link

I would also really like this as well. Especially since CREATE INDEX CONCURRENTLY. Right now if you add an index to a hypertable it will lock and you're not sure when it will become available again.

At least for me...if CONCURRENTLY and this take the same amount of work, I would prefer CONCURRENTLY 😄

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

No branches or pull requests

4 participants