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

[Bug]: time_bucket_gapfill is not gapfilling after upgrade to 2.13.0 #6385

Closed
MA-MacDonald opened this issue Dec 7, 2023 · 2 comments
Closed
Labels

Comments

@MA-MacDonald
Copy link

MA-MacDonald commented Dec 7, 2023

What type of bug is this?

Other

What subsystems and features are affected?

Gapfill

What happened?

After upgrading from v2.10.3 to v2.13.0 time_bucket_gapfill is not filling gaps.
If there is no data in the time range it returns no rows.

SELECT
  time_bucket_gapfill('1 day', time) AS date,
  SUM(metric) AS metric
FROM table
WHERE time >= '2021-01-01' AND time < '2022-01-01' 
GROUP BY 1
ORDER BY 1 DESC;

Running the above query on v2.10.3 returns the expected output.
image

Running the above query on v2.13.0 returns no data.
image

TimescaleDB version affected

2.13.0

PostgreSQL version used

16

What operating system did you use?

Windows 10 Enterprise x64

What installation method did you use?

Not applicable

What platform did you run on?

On prem/Self-hosted

Relevant log output and stack trace

No response

How can we reproduce the bug?

Explained in description
@antekresic
Copy link
Contributor

Hi there,

I've tried reproducing this issue but was unsuccessful.

Would you mind giving me a step by step reproduction case so I can try this?

I've tried this on Windows as well but did not get the problem you are getting.

Thanks.

@MA-MacDonald
Copy link
Author

Hi @antekresic thanks for checking this out.

I did some more testing and when I tried to create a new hypertable I got the following error:
ERROR: tried calling catalog_get when extension isn't loaded
Googling led me to these issues #1682, #1844

I did a new backup of the source db on pg15 and restored again on the new db on pg16 and the issue went away.
I'm guessing there was some issue when upgrading from pg15 to pg16.

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

2 participants