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 1uFaVy-006FiP-FF for pgsql-bugs@arkaria.postgresql.org; Thu, 15 May 2025 15:28:54 +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 1uFaVx-00FJEv-9O for pgsql-bugs@arkaria.postgresql.org; Thu, 15 May 2025 15:28:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uFaVx-00FJEn-11 for pgsql-bugs@lists.postgresql.org; Thu, 15 May 2025 15:28:53 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uFaVu-001wOa-17 for pgsql-bugs@lists.postgresql.org; Thu, 15 May 2025 15:28:52 +0000 Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 54FFSiBe1775010; Thu, 15 May 2025 11:28:45 -0400 From: Tom Lane To: jinhuilai@email.ncu.edu.cn cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table In-reply-to: <18933-85d850c7526716f6@postgresql.org> References: <18933-85d850c7526716f6@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 15 May 2025 13:42:30 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11835.1747322924.1@sss.pgh.pa.us> Date: Thu, 15 May 2025 11:28:44 -0400 Message-ID: <11836.1747322924@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Obviously, the above queries always returns an empty set. I think it should > return an empty set quickly. None of these things are bugs. You are accomplishing little except to annoy people, especially when the more appropriate way to proceed was already explained to you a few weeks ago. regards, tom lane