public inbox for [email protected]
help / color / mirror / Atom feedFrom: Christoph Moench-Tegeder <[email protected]>
To: Andreas Joseph Krogh <[email protected]>
Cc: [email protected]
Subject: Re: AI for query-planning?
Date: Sat, 22 Jun 2024 17:21:07 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <VisenaEmail.38.c31ee0594849fa9d.1903fc67a71@origo-test01.app.internal.visena.net>
References: <VisenaEmail.38.c31ee0594849fa9d.1903fc67a71@origo-test01.app.internal.visena.net>
## Andreas Joseph Krogh ([email protected]):
> Hi, are there any plans for using some kind of AI for query-planning?
Actually, we do have our GEQO - Genetic Query Optimization - already
in the planner: https://www.postgresql.org/docs/current/geqo.html
As per the common taxomonies, genetic algorithms are part of the
larger "Artificial Intelligence" domain - they're just not part of
the current hype cycle (some of us still remember the early iterations
of neuronal networks, or fuzzy logic, or...).
> Can someone with more knowledge about this than I have please explain why it
> might, or not, be a good idea, and what the challenges are?
Just waving your hand and saying "AI" three times in a row does not
manifest an usable algorithm. Going the full way from a problem to be
understood and solved to algorithm to implementation requires more
effort - and especially with all the "hot off the hype press" ideas
that already fails in the very first stages. Remember just recently,
when some people were "predicting" that all databases would become
blockchains?
Regards,
Christoph
--
Spare Space
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: AI for query-planning?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox