-
Notifications
You must be signed in to change notification settings - Fork 848
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]: 'ERROR: tuple already updated by self' after inserting data when chunk was dropped #6904
Comments
Do you have any old-format continuous aggregates? You can check with |
This query gives me no results. All the hypertables, ontinuous aggregates etc. were created about 1 month ago. |
Any chance you can upgrade to 2.15.1 to confirm if this is still a problem with the latest version? This might have been fixed by some of the catalog update work we did there. Thanks, |
What type of bug is this?
Unexpected error
What subsystems and features are affected?
Data ingestion
What happened?
Chunks were dropped from a hypertable by retention policy. When I insert a new row that would be in those chunks I am getting ERROR:
tuple already updated by self
.TimescaleDB version affected
2.14.2
PostgreSQL version used
16.2
What operating system did you use?
22.04.4
What installation method did you use?
Deb/Apt
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
No response
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: