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 1nWmCZ-0001Zy-Al for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Mar 2022 21:38:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWmCY-0005a8-9p for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Mar 2022 21:38:02 +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 1nWmCY-0005Zz-0Z for pgsql-hackers@lists.postgresql.org; Tue, 22 Mar 2022 21:38:02 +0000 Received: from relay8-d.mail.gandi.net ([2001:4b98:dc4:8::228]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWmCV-0002Vd-7H for pgsql-hackers@postgresql.org; Tue, 22 Mar 2022 21:38:00 +0000 Received: (Authenticated sender: adsend@dunslane.net) by mail.gandi.net (Postfix) with ESMTPSA id D24F51BF206; Tue, 22 Mar 2022 21:37:52 +0000 (UTC) Message-ID: <8500cf09-d5eb-eafe-4794-25b0a377a3ce@dunslane.net> Date: Tue, 22 Mar 2022 17:37:50 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: SQL/JSON: JSON_TABLE Content-Language: en-US From: Andrew Dunstan To: Alvaro Herrera Cc: Oleg Bartunov , Matthias Kurz , Himanshu Upadhyaya , Julien Rouhaud , Erik Rijkers , Nikita Glukhov , PostgreSQL-development , Pavel Stehule , Dmitry Dolgov <9erthalion6@gmail.com> References: <202203221453.krbzphuczrou@alvherre.pgsql> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/22/22 11:27, Andrew Dunstan wrote: > On 3/22/22 10:53, Alvaro Herrera wrote: >> On 2022-Mar-22, Andrew Dunstan wrote: >> >>> I'm planning on pushing the functions patch set this week and json-table >>> next week. >> I think it'd be a good idea to push the patches one by one and let a day >> between each. That would make it easier to chase buildfarm issues >> individually, and make sure they are fixed before the next step. >> Each patch in each series is already big enough. > > > OK, can do it that way. First one will be later today then. > > OK, pushed the first of the functions patches. That means the cfbot will break on these two CF items, but it's way too much trouble to have to remake the patch sets every day, so we can just live without the cfbot on these for a bit. I will of course test before committing and fix any bitrot. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com