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 1nWoYX-0001KN-39 for pgsql-committers@arkaria.postgresql.org; Wed, 23 Mar 2022 00:08:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWoYV-0004i6-Uq for pgsql-committers@arkaria.postgresql.org; Wed, 23 Mar 2022 00:08:51 +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 1nWoYV-0004hx-Nf for pgsql-committers@lists.postgresql.org; Wed, 23 Mar 2022 00:08:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWoYT-0001q6-Ke for pgsql-committers@lists.postgresql.org; Wed, 23 Mar 2022 00:08:51 +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 22N08jIu2630815; Tue, 22 Mar 2022 20:08:45 -0400 From: Tom Lane To: Andrew Dunstan cc: Andres Freund , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Common SQL/JSON clauses In-reply-to: <9fee834f-ddd9-2adb-0d6f-4ad5af92c12b@dunslane.net> References: <20220322223319.so4ajcki7wwaujin@alap3.anarazel.de> <9fee834f-ddd9-2adb-0d6f-4ad5af92c12b@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Tue, 22 Mar 2022 19:21:26 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2630813.1647994125.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 22 Mar 2022 20:08:45 -0400 Message-ID: <2630814.1647994125@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 3/22/22 18:33, Andres Freund wrote: >> This currently triggers a number of warnings. I assume that's because o= f the >> following patches not being there yet? How far out are those? > Tomorrow, with the SQL/JSON constructors patch should resolve it. So > roughly 24 hours. It's not his fault but this happened because Alvaro > asked me to stagger the commits. Sounds like all you have to do is merge this commit with the next one in the series? Might as well do it if so. But please don't push something that generates warnings. regards, tom lane