Predicting query runtime - Mailing list pgsql-general

From Vinicius Segalin
Subject Predicting query runtime
Date
Msg-id CAAeH1nDyLp+vAzEbiC4WgP08=SGvAvyTA2uX9ee1XMrNGf+MZg@mail.gmail.com
Whole thread Raw
Responses Re: Predicting query runtime  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
Re: Predicting query runtime  (Merlin Moncure <mmoncure@gmail.com>)
Re: Predicting query runtime  (Jeff Janes <jeff.janes@gmail.com>)
Re: Predicting query runtime  (Istvan Soos <istvan.soos@gmail.com>)
Re: Predicting query runtime  (Oleg Ivanov <o.ivanov@postgrespro.ru>)
List pgsql-general
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.

Thank you.

Best regards,

Vinicius Segalin

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: [SPAM] Re: Question about locking and pg_locks
Next
From: Oleksandr Shulgin
Date:
Subject: Re: Predicting query runtime