public inbox for [email protected]
help / color / mirror / Atom feedFrom: Pyrote <[email protected]>
To: [email protected]
Subject: Re: AI for query-planning?
Date: Sat, 22 Jun 2024 10:23:36 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <VisenaEmail.38.c31ee0594849fa9d.1903fc67a71@origo-test01.app.internal.visena.net>
<[email protected]>
<div dir="auto">The current forms of “AI” have no concept of state or long term memory. On each invocation of the AI you have to tell it,</div><div dir="auto"><br></div><div dir="auto">This is a Postgres database.</div><div dir="auto"><br></div><div dir="auto">This is my database schema.</div><div dir="auto"><br></div><div dir="auto">These are the indexes I have.</div><div dir="auto"><br></div><div dir="auto">After providing that information the “AI” “might” generate a valid query for your particular database but it won’t be optimum. The AI doesn’t know how many rows are in each table, the physical media each table is on, or any other attributes about your database that would be used to calculate the cost of using an index or a table scan.</div><div dir="auto"><br></div><div dir="auto">So then you could make the jump that an “AI” should be ran locally and trained exclusively on your database. Now you are using a general purpose “AI” algorithm for a very specific task which would not be optimum. It would require constant retraining which would be computationally expensive. </div><div dir="auto"><br></div><div dir="auto">Then let’s say you want to write an “AI” algorithm just for Postgres. Now you have basically rewritten the current Postgres Optimizer in a round about way. </div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 22, 2024 at 09:40 Adrian Klaver <[email protected]> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On 6/22/24 04:50, Andreas Joseph Krogh wrote:
<br>> Hi, are there any plans for using some kind of AI for query-planning?
<br>>
<br>> Can someone with more knowledge about this than I have please explain
<br>> why it might, or not, be a good idea, and what the challenges are?
<br>
<br>1) Require large amount of resources.
<br>
<br>2) Produce high rate of incorrect answers.
<br>
<br>
<br>>
<br>> Thanks.
<br>>
<br>> --
<br>> *Andreas Joseph Krogh*
<br>> CTO / Partner - Visena AS
<br>> Mobile: +47 909 56 963
<br>> [email protected] <mailto:[email protected]>
<br>> www.visena.com <https://www.visena.com>
<br>> <https://www.visena.com>
<br>
<br>--
<br>Adrian Klaver
<br>[email protected]
<br>
<br>
<br>
<br></blockquote></div></div>
view thread (2+ messages)
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]
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