pg_query_state
pg_query_state copied to clipboard
postgrespro
Tool for query progress monitoring in PostgreSQL
Thanks for the great extension. Tried it on PG 14.1, and had the following issues: 1. TIMING and BUFFERS are not working – tried to set it everywhere, on both...
On "slow" runs we can get something like this: ```============== running regression test queries ============== test corner_cases ... FAILED 8738 ms ====================== 1 of 1 tests failed. ====================== The differences...
I have added TCP-DS in a separate PR https://github.com/postgrespro/pg_query_state/pull/17, since it is difficult to do two huge things at once (migrating to [testgres](https://github.com/postgrespro/testgres) and adding TCP-DS). Although I still think...
There are two types of errors occurring from time to time when running docker tests. 1) Assertion failure with basic python tests: ``` test when two backends compete with each...
Rework existing PR https://github.com/postgrespro/pg_query_state/pull/16 and migrate current python tests to [testgres](https://github.com/postgrespro/testgres) Postgres testing framework.
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...
Hello, pg_query_state is really a cool tool and I'm recently learning through the code. I noticed the process needs to check if n_peers is zero or wait a timeout before...
1) Add patches for PostgreSQL 17; 2) Add alternative output to python test due to EXPLAIN output change. See fd0398fcb099.
Metadata
Owner
Metadata
Tool for query progress monitoring in PostgreSQL