MironAtHome commented on issue #1925: URL: https://github.com/apache/age/issues/1925#issuecomment-2214977144
There are a few troubleshooting approaches I learned over the last week - end. Please let me know if you are open to installing extensions, that can help to expose detailed wait information, regarding where query spends time, and turning on some of the troubleshooting options. [This](https://github.com/postgrespro/sr_plan), [this](https://github.com/postgrespro/pg_query_state) and [this](https://github.com/postgrespro/pg_wait_sampling). Feel free to add a comment here. Please don't just install these extensions, but rather see if those meet your Postgres version and see if ( entirely possible ) there are native, postgres itself, maintained extensions, or even built - in functions, that provide same level of troubleshooting. This first step is just to ensure proper tooling is in place to attempt to identify slower parts of query prior attempting to fix. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
