Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sL29Z-00D9Sl-ON for pgsql-general@arkaria.postgresql.org; Sat, 22 Jun 2024 14:55:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sL29X-009v8l-Uj for pgsql-general@arkaria.postgresql.org; Sat, 22 Jun 2024 14:55:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sL29X-009v8H-Jb for pgsql-general@lists.postgresql.org; Sat, 22 Jun 2024 14:55:43 +0000 Received: from mail-lf1-x144.google.com ([2a00:1450:4864:20::144]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sL29V-002zz9-C0 for pgsql-general@postgresql.org; Sat, 22 Jun 2024 14:55:43 +0000 Received: by mail-lf1-x144.google.com with SMTP id 2adb3069b0e04-52cdf579dd2so386228e87.3 for ; Sat, 22 Jun 2024 07:55:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719068140; x=1719672940; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=d9zSnpcvX953AeHhKf2Vc6G7NuvEjtz6t8q2cxHtAnI=; b=iTwC1ErAVPHT213pWJH21xkSEDI3OdQwT+E/W2t8QkxOLvh0+UYBXS72Dc4/r9braF Jckyuvcn1OmPbIN/Nw5bnXFUY7+HrAHjpP4AuvXNxB3EFdd/XHxNJIJdv3KxIEZFBPT1 JQSApGoQ92SQb2OQberO0Hh2m3teR+czl63Wf9pQk3qVqR7T//GT6woghQPD6Jduc5s5 4NKITG18U4zBF4ur7lKSRKTFGrNNu1Vrb+j4GJBPxhg2gyHpv/ogp2eWihvSL6i4iFUD oUp/WNqwtFEZlBpfRrhXzTdOKcy11W05xnsSHZXso+yws3u7cqibNxn2+6psLC48J3eO /X8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719068140; x=1719672940; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=d9zSnpcvX953AeHhKf2Vc6G7NuvEjtz6t8q2cxHtAnI=; b=P5nWXE85hV7n8OjaF3LZg4tlmnqxNI3zocMjTZdZGVH+A1VoIyyNgniLl9KZvJ/wCJ Fuk8dGBcbfgLEqTR3yO0Lv298V+wz6xXhcmvMvr9zGtB9zlNZXqH70DPZpz/TiigDo0m DxhCwQNfP90toxJoRW3r4EKVOVRiU4uFRLk24sg9H+w+I1MsmR8Vf0dCqKZ5ePxcqApG 7poApadZC1gWNRJ2yQanrQmIHaxTRCgIuPryfqCQncp1B3f3sBxA7+I1mGnDwIJ3221E vrrYn5MCj8fvDEn4Dpy17/1zXZZOplKh8fl+WP9CA5VdSWCkZu69jcn0aLvmg9PhV+Hl f7Eg== X-Gm-Message-State: AOJu0YzxqcFAjNt+h/wdMwL0ESrtyNN0kvmgCEZzKTcZRoUJgV2eBrNs 4tMpmmn1EoZjG7SpNylFc4CzDFz2v4DimQvjwtfZG+48okO50+vDopF7VqEIORjbbBHqbGwTcox MSRb1P18EiXzZfSSfVX5dCLlQNeU= X-Google-Smtp-Source: AGHT+IE09b9Gc6jwBlKf36hMrqtGgd2GBLDNXnfElnd/RWZlHybijwK99stYvzENli+OZuczygxJw4GGypqGoX9qlX4= X-Received: by 2002:a19:5e56:0:b0:52c:81fc:eba2 with SMTP id 2adb3069b0e04-52cdf8209ddmr693374e87.44.1719068139883; Sat, 22 Jun 2024 07:55:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Vijaykumar Jain Date: Sat, 22 Jun 2024 20:25:29 +0530 Message-ID: Subject: Re: AI for query-planning? To: Andreas Joseph Krogh Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000d29a49061b7bbdc7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d29a49061b7bbdc7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jun 22, 2024, 5:20=E2=80=AFPM Andreas Joseph Krogh wrote: > Hi, are there any plans for using some kind of AI for query-planning? > > 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? > https://github.com/ossc-db/pg_plan_advsr https://github.com/s-hironobu/pg_plan_inspector not totally ai, but it can use data from your database to build some metadata. there are also plan analyzers online which people paste their plan to get a quick summary of problem areas, that data can be useful too for ai based plan optimisers. but that said, postgresql has a lot of knobs to tune, so ... --000000000000d29a49061b7bbdc7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



--000000000000d29a49061b7bbdc7--