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

[PGPRO-8358] Added the progress value to the pg_query_state message #58

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

arseny114
Copy link
Contributor

The progress value is equal to the actual_rows ratio to plan_rows as a percentage.
Or 100% if actual_rows > plan_rows. The progress value is added for each node in the current_loop.
The progress value is added to the message taking into account the format (TEXT, XML, JSON, YAML)
and provided that the parameter costs = true.

Tags: pg_query_state

Ekaterina Sokolova and others added 4 commits August 11, 2024 15:03
Progress bar is run-time SQL-query progress indicator.

Function progress_bar(pid) extracts the current query state from backend with specified 'pid'. Then gets the numerical values of the actual rows
and total rows and count progress for the whole query tree. Function returns numeric value from 0 to 1 describing the measure of query fulfillment.
This function can be used to be embedded in the PostgreSQL GUI.

To intuitively track progress without using a graphical client, you can use the additionally implemented function progress_bar_visual(pid, delay).
It prints state every period specified by 'delay' (in seconds).
The progress value is equal to the actual_rows ratio to plan_rows as a percentage.
Or 100% if actual_rows > plan_rows. The progress value is added for each node in the current_loop.
The progress value is added to the message taking into account the format (TEXT, XML,
JSON, YAML) and provided that the parameter costs = true.

Tags: pg_query_state
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

Successfully merging this pull request may close these issues.

1 participant