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 1puFiA-0002gX-UB for pgsql-hackers@arkaria.postgresql.org; Wed, 03 May 2023 16:52:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1puFi9-0003D9-Bi for pgsql-hackers@arkaria.postgresql.org; Wed, 03 May 2023 16:52:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1puFi9-0003D0-1A for pgsql-hackers@lists.postgresql.org; Wed, 03 May 2023 16:52:13 +0000 Received: from mail-pf1-x436.google.com ([2607:f8b0:4864:20::436]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1puFi5-000NNg-TU for pgsql-hackers@postgresql.org; Wed, 03 May 2023 16:52:12 +0000 Received: by mail-pf1-x436.google.com with SMTP id d2e1a72fcca58-63b4e5fdb1eso5927957b3a.1 for ; Wed, 03 May 2023 09:52:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=irregular.at; s=google; t=1683132728; x=1685724728; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XfE2IWQi+1qB6Zl/BtgEauxuRcvDwJHgRpiWDlfAYBQ=; b=S+TWgLeJcJU2PvbIL6kvhfvhCmH2yqDmpf+QhQ99mDPmPPg7OB/XsjkNHZmeckT2Ej uBhu9fdnJQiPLMv53SpQl/YlY38AX4AlK6NK/qTKVZzkNlgvvp/BEMi/VPU/5ZXdpFSV T0HtC8GbX0BJLqvDukbLGyIH2y4YAmkQt99zo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683132728; x=1685724728; 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=XfE2IWQi+1qB6Zl/BtgEauxuRcvDwJHgRpiWDlfAYBQ=; b=lTVMlN7zXTyM3ewNJxUuZ9kG0TU60xkyuP3w/bXam45fLd1hzF0Qz0II3Dk5jFcj+M Im41fIHr3Z7kFrj6tdLXZ+GoSxMuaB7pZMKT8c8oKkHueO/8IBmT632o8pHvKTO13SVr +migaeu0GZGcN9XqGJrpRem4uuyLtfqCKUn0OROTtwScwr1zIXXLcHpEgOCRumtHGhgk 1gmXXggrUyc3by/zKlPoCJjQfiSOHuCB//nVQwAcITnDcGM4ZTis0kZcNqAhte6q3upO I5Fm5BCQC1y1neIl+uDZt1Ze5Qh/gUafUgW61wgkR31uPv+GIjKGRty9bJRq6+gFzp6s 52JQ== X-Gm-Message-State: AC+VfDyZusWl5t+cSCvV7U2iKgG5/SwAn3C9mj1Q+wcySho39nROmmM9 XzdNBhBNjj6ZmfZUE8sGD37jNt1o3PBmno4u9t5BWQ== X-Google-Smtp-Source: ACHHUZ7JXOdNBEd7ZIBi4yU4E0U20XfjuQi2+IQJp5AOZkNt0+SqzaIdNDXgDbZI+MsubBWHm1SgKXiPUM0S8IoZSk8= X-Received: by 2002:a05:6a21:3007:b0:f0:322a:d84e with SMTP id yd7-20020a056a21300700b000f0322ad84emr20225519pzb.36.1683132727762; Wed, 03 May 2023 09:52:07 -0700 (PDT) MIME-Version: 1.0 References: <20230405072329.kpx37fw4l5yfechq@alvherre.pgsql> In-Reply-To: <20230405072329.kpx37fw4l5yfechq@alvherre.pgsql> From: Matthias Kurz Date: Wed, 3 May 2023 18:51:56 +0200 Message-ID: Subject: Re: SQL/JSON revisited To: Alvaro Herrera Cc: Andrew Dunstan , Amit Langote , Alexander Lakhin , Erik Rijkers , Peter Eisentraut , Andres Freund , vignesh C , PostgreSQL-development , e.indrupskaya@postgrespro.ru Content-Type: multipart/alternative; boundary="00000000000059365d05facce032" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000059365d05facce032 Content-Type: text/plain; charset="UTF-8" On Wed, 5 Apr 2023 at 09:53, Alvaro Herrera wrote: > > Okay, I've marked the CF entry as committed then. > This was marked as commited in the 2023-03 commitfest, however there are still patches missing (for example the JSON_TABLE one). However, I can not see an entry in the current 2023-07 Commitfest. I think it would be a good idea for a new entry in the current commitfest, just to not forget about the not-yet-commited features. Thanks! Matthias --00000000000059365d05facce032 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, 5 Apr 2023 at 09:53, Alvaro Herre= ra <alvherr= e@alvh.no-ip.org> wrote:

Okay, I've marked the CF entry as committed then.
=
This was marked as commited in the 2023-03 commitfest, howev= er there are still patches missing (for example the JSON_TABLE one).
<= div>However, I can not see an entry in the current 2023-07 Commitfest.
I think it would be a good idea for a new entry in the current commit= fest, just to not forget about the not-yet-commited features.
Thanks!
Matthias
--00000000000059365d05facce032--