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

Execution time much bigger than the first node total runtime #621

Open
gleu opened this issue Jan 23, 2024 · 0 comments
Open

Execution time much bigger than the first node total runtime #621

gleu opened this issue Jan 23, 2024 · 0 comments

Comments

@gleu
Copy link
Member

gleu commented Jan 23, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant