Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDaeM-0005nj-Lj for pgsql-bugs@arkaria.postgresql.org; Mon, 08 Apr 2019 20:13:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hDaeL-0003QA-14 for pgsql-bugs@arkaria.postgresql.org; Mon, 08 Apr 2019 20:13:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDaeK-0003Mm-Me for pgsql-bugs@lists.postgresql.org; Mon, 08 Apr 2019 20:13:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hDaeI-0007Pr-5g for pgsql-bugs@lists.postgresql.org; Mon, 08 Apr 2019 20:13:47 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x38KDgAi019732; Mon, 8 Apr 2019 16:13:42 -0400 From: Tom Lane To: skorski.anthony@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15741: ERROR: failed to build any 3-way joins In-reply-to: <30020.1554732838@sss.pgh.pa.us> References: <15741-276f1f464b3f40eb@postgresql.org> <30020.1554732838@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 08 Apr 2019 10:13:58 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19730.1554754422.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 08 Apr 2019 16:13:42 -0400 Message-ID: <19731.1554754422@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > PG Bug reporting form writes: >> Trying to build a tool which automatically builds queries to "flatten" = JSONB >> fields, I came to a `ERROR: failed to build any 3-way joins` message wh= ile >> trying to execute some of those queries. > Yeah, that's certainly a bug. I'll take a look later ... Fixed at https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommitdiff;h=3D0= 51c71c6746309782d9bf1ebb257d3b5f88e6fb7 regards, tom lane