Open shhnwz opened 1 year ago
Hi there we've got similar issue on PostgreSQL version 15.5 TimescaleDB version v2.13.0 (latest)
LOG: process 1729351 still waiting for ShareLock on relation 18907 of database 16466 after 9997.774 ms
Any updates here?
Same here, waiting for updates. Thanks!
We are also experiencing this issue! Also waiting for updates.
Hi there,
There have been recent changes with the way we handle foreign key constraints recently.
Would you mind confirming that this still an issue with the latest version 2.15? For the record, I tried the repro case locally and it seemed to not cause a deadlock with version 2.15 on PG 16
Thanks!
Hi @antekresic,
Thank you for your notice.
After having tried to reproduce the issue locally with the latest version 2.15 on PG 15.7, I can gladly confirm that the instruction I originally came up with no longer causes the deadlock as decompress_chunk
does not acquire ShareRowExclusiveLock
on devices
anymore.
As for production environment in which the issue initially occurred, unfortunately I cannot check if it's gone because we ended up dropping the constraint.
I would personally consider this one resolved.
Can confirm that our issue is also fixed on version 2.15.2 on PG 14.
What type of bug is this?
Locking issue
What subsystems and features are affected?
Query executor
What happened?
Cyclic lock dependency occurs whenever concurrent operations involves Hypertable [HT] having referential integrity (Foreign Key) defined with plain table [T].
Reported Customer Scenarios:
https://github.com/timescale/timescaledb/issues/4800 https://github.com/timescale/timescaledb/issues/5325
TimescaleDB version affected
2.7.0
PostgreSQL version used
14.1
What operating system did you use?
Ubuntu 20.04 x64
What installation method did you use?
Not applicable
What platform did you run on?
Managed Service for TimescaleDB (MST/Aiven)
Relevant log output and stack trace
No response
How can we reproduce the bug?