Query Progress (was: Performance With Joins on Large Tables)
От | Bucky Jordan |
---|---|
Тема | Query Progress (was: Performance With Joins on Large Tables) |
Дата | |
Msg-id | 78ED28FACE63744386D68D8A9D1CF5D4104D08@MAIL.corp.lumeta.com обсуждение исходный текст |
Ответ на | Re: Performance With Joins on Large Tables ("Joshua Marsh" <icub3d@gmail.com>) |
Ответы |
Re: Query Progress (was: Performance With Joins on Large Tables)
|
Список | pgsql-performance |
Setting to 0.1 finally gave me the result I was looking for. I know that the index scan is faster though. The seq scan never finished (i killed it after 24+ hours) and I'm running the query now with indexes and it's progressing nicely (will probably take 4 hours). In regards to "progressing nicely (will probably take 4 hours)" - is this just an estimate or is there some way to get progress status (or something similar- e.g. on step 6 of 20 planned steps) on a query in pg? I looked through Chap 24, Monitoring DB Activity, but most of that looks like aggregate stats. Trying to relate these to a particular query doesn't really seem feasible. This would be useful in the case where you have a couple of long running transactions or stored procedures doing analysis and you'd like to give the user some feedback where you're at. Thanks, Bucky
В списке pgsql-performance по дате отправления: