You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if you deal with hints now, but if you are, if there is a much bigger execution time (last line) than the first node total runtime, it might be because it's waiting for locks. See https://explain.dalibo.com/plan/20205991261113ga for an example. The query lasts 22 seconds for the user, but PostgreSQL finishes after 11 seconds. The remaining is lost on waiting for locks (I had a VACUUM FULL running on the table).
The text was updated successfully, but these errors were encountered:
Not sure if you deal with hints now, but if you are, if there is a much bigger execution time (last line) than the first node total runtime, it might be because it's waiting for locks. See https://explain.dalibo.com/plan/20205991261113ga for an example. The query lasts 22 seconds for the user, but PostgreSQL finishes after 11 seconds. The remaining is lost on waiting for locks (I had a VACUUM FULL running on the table).
The text was updated successfully, but these errors were encountered: