From: Tom Lane <tgl@sss.pgh.pa.us>
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
Date: Thu, 15 May 2025 11:28:44 -0400
Message-ID: <11836.1747322924@sss.pgh.pa.us> (raw)
In-Reply-To: <18933-85d850c7526716f6@postgresql.org>
References: <18933-85d850c7526716f6@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, jinhuilai@email.ncu.edu.cn, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18933: PostgreSQL fails to handle JOIN operation involving Empty Table
In-Reply-To: <11836.1747322924@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox