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 1qw1Pl-0095Sf-63 for pgsql-general@arkaria.postgresql.org; Thu, 26 Oct 2023 14:32:49 +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 1qw1Pj-000z6d-Fg for pgsql-general@arkaria.postgresql.org; Thu, 26 Oct 2023 14:32:47 +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 1qw1Pj-000z5f-4M for pgsql-general@lists.postgresql.org; Thu, 26 Oct 2023 14:32:47 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qw1Pf-002w5K-9b for pgsql-general@lists.postgresql.org; Thu, 26 Oct 2023 14:32:46 +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 39QEWbVG1159950; Thu, 26 Oct 2023 10:32:37 -0400 From: Tom Lane To: Anders Kildemand cc: "pgsql-general@lists.postgresql.org" Subject: Re: Question regarding the new SQL standard In-reply-to: References: Comments: In-reply-to Anders Kildemand message dated "Thu, 26 Oct 2023 12:37:59 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1159948.1698330757.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 26 Oct 2023 10:32:37 -0400 Message-ID: <1159949.1698330757@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Anders Kildemand writes: > What's the situation with Property Graph Queries in Postgres? There isn't any. > I've heard that it has become part of the SQL standard from this blog: h= ttps://peter.eisentraut.org/blog/2023/04/04/sql-2023-is-finished-here-is-w= hats-new > How far in development is this feature? and is there an expected time fr= ame for when it'll be finished? I think you have a fundamental misunderstanding about how Postgres development works. There is plenty of stuff in the standard that nobody has any particular interest in implementing for PG. Perhaps someone will take an interest in implementing this feature, or perhaps not. But there's no project-wide goal to make it happen, much less a timetable. Even if someone does take an interest, they might not succeed in producing a committable patch. regards, tom lane