Re: Anti join confusion

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Anti join confusion
Date: 2025-02-24 13:08:06
Message-ID: CAGjGUA+fK6WCakPzy+Xmr8jmJLuht11+WxmiJ+je3CFRuJszRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Laurenz
Actually ,Many fork postgresql databases have already implemented ,For
example, if the relevant field has a non-null constraint ,Many databases
can do the same thing as not exist ( MySQL ,SQL Server,Oracle)

Thanks

On Mon, Feb 24, 2025 at 7:55 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Mon, 2025-02-24 at 17:12 +0800, wenhui qiu wrote:
> > Do we have plans for NOT IN subquery pull up?
>
> As mentioned before, that is not possible.
> Best practice is to avoid NOT IN with subqueries altogether.
> The result is usually not what people expect it to be.
>
> Yours,
> Laurenz Albe
>
> --
>
> *E-Mail Disclaimer*
> Der Inhalt dieser E-Mail ist ausschliesslich fuer den
> bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat
> dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
> dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung
> oder
> Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich
> in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
>
> *CONFIDENTIALITY NOTICE & DISCLAIMER
> *This message and any attachment are
> confidential and may be privileged or otherwise protected from disclosure
> and solely for the use of the person(s) or entity to whom it is intended.
> If you have received this message in error and are not the intended
> recipient, please notify the sender immediately and delete this message
> and
> any attachment from your system. If you are not the intended recipient, be
> advised that any use of this message is prohibited and may be unlawful,
> and
> you must not copy this message or attachment or disclose the contents to
> any other person.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2025-02-24 13:33:34 Re: RFC: Additional Directory for Extensions
Previous Message Bertrand Drouvot 2025-02-24 13:08:03 Re: Remove wal_[sync|write][_time] from pg_stat_wal and track_wal_io_timing