Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qCeci-00008Q-II for pgsql-general@arkaria.postgresql.org; Fri, 23 Jun 2023 11:06:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qCecg-0005o0-CO for pgsql-general@arkaria.postgresql.org; Fri, 23 Jun 2023 11:06:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qCecg-0005kG-14 for pgsql-general@lists.postgresql.org; Fri, 23 Jun 2023 11:06:38 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qCecd-003nZ2-Gi for pgsql-general@lists.postgresql.org; Fri, 23 Jun 2023 11:06:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 35NB6Wf4013885; Fri, 23 Jun 2023 07:06:32 -0400 From: Tom Lane To: Michael Paquier cc: Juan Rodrigo Alejandro Burgos Mella , pgsql-general@lists.postgresql.org Subject: Re: ECPG Semantic Analysis In-reply-to: References: Comments: In-reply-to Michael Paquier message dated "Fri, 23 Jun 2023 14:01:13 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13883.1687518392.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 23 Jun 2023 07:06:32 -0400 Message-ID: <13884.1687518392@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > On Fri, Jun 23, 2023 at 12:21:48AM -0400, Juan Rodrigo Alejandro Burgos = Mella wrote: >> I have a modified version of ECPG, to which I gave the ability to do >> semantic analysis of SQL statements. Where can you share it or with who= m >> can I discuss it? > I cannot say what kind of problem this solves and/or if this is useful > as a feature of the ECPG driver in PostgreSQL core itself, but you > could consider submitting a patch for integration into core. TBH I'd have to discourage you from expecting that such a patch would be accepted. ECPG is pretty much of a development backwater nowadays. We keep maintaining it because it's (mostly) not too much trouble thanks to the work that was done years ago to auto-generate its grammar from the main grammar. However, adding any sort of semantic analysis to it seems like it'd take an enormous amount of new C code that would then have to be kept in sync (by hand) with the backend parser. Testing such a thing seems like a big time sink as well. I seriously doubt that we'd be willing to take on such a maintenance burden. regards, tom lane