Re: Predicting query runtime
От | Hu, Patricia |
---|---|
Тема | Re: Predicting query runtime |
Дата | |
Msg-id | A22137031445794A99E795CDDB6BAF588C54275C@KWAWNEXMBP002.corp.root.nasd.com обсуждение исходный текст |
Ответ на | Re: Predicting query runtime (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>) |
Список | pgsql-general |
I’ve been looking for this on postgres too. Does Postgres have something similar to Oracle’s v$session_longops? It gives info on total unit of work, units done so far, last update time, and time remaining etc, and I found it valuable in providing an estimate to how long a certain query would keep running and whether or not to kill it if applicable. This should be relatively easy to implement in postgres too if it is not available yet?
Thanks,
Patricia
From: Oleksandr Shulgin [mailto:oleksandr.shulgin@zalando.de]
Sent: Monday, September 12, 2016 11:08 AM
To: Vinicius Segalin
Cc: pgsql general
Subject: Re: Predicting query runtime
On Mon, Sep 12, 2016 at 4:03 PM, Vinicius Segalin <vinisegalin@gmail.com> wrote:
Hi everyone,
I'm trying to find a way to predict query runtime (I don't need to be extremely precise). I've been reading some papers about it, and people are using machine learning to do so. For the feature vector, they use what the DBMS's query planner provide, such as operators and their cost. The thing is that I haven't found any work using PostgreSQL, so I'm struggling to adapt it.
My question is if anyone is aware of a work that uses machine learning and PostgreSQL to predict query runtime, or maybe some other method to perform this.
Hi,
I'm not aware of machine-learning techniques to achieve that (and I don't actually believe it's feasible), but there you might find this extension particularly useful: https://www.postgresql.org/docs/9.5/static/pgstatstatements.html[postgresql.org]
Can you share some links to the papers you are referring to (assuming these are publicly available)?
Regards,
--
Alex
В списке pgsql-general по дате отправления: