-
Notifications
You must be signed in to change notification settings - Fork 686
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
M3hm3t/debug upgrade test #7862
base: naisila/test-upgrade
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
❌ Your patch check has failed because the patch coverage (50.00%) is below the target coverage (75.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## naisila/test-upgrade #7862 +/- ##
========================================================
- Coverage 89.42% 85.43% -3.99%
========================================================
Files 276 276
Lines 60071 60069 -2
Branches 7524 7526 +2
========================================================
- Hits 53718 51322 -2396
- Misses 4202 6318 +2116
- Partials 2151 2429 +278 |
Process 95617 is waiting for an AccessExclusiveLock on relation 16541, which is held by process 95618. Process 95618 is running as the Citus Maintenance Daemon (state: Extension). Locks are being held on key catalog tables: The |
It seems like the issue comes up because
I’m guessing this has become more noticeable with PostgreSQL 15, maybe due to changes in locking behavior or deadlock detection, but I’m not 100% sure. |
Added retries with an exponential backoff to handle temporary deadlocks in the This points to the deadlock being a short-term issue, probably due to some lock contention between the |
Debugging the This comment in Also, I didn't observe the issue in my debug session, the |
However, looks like maintenance deamon only sporadically checks for this condition. |
I tried disabling the Citus daemon for the Could you take a look as well? I’m not sure if this is the right approach to pursue.
|
extended logs:
|
DESCRIPTION: PR description that will go into the change log, up to 78 characters