pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bernd von den Brincken <bvdb@asa.de>
To: pgsql-sql@postgresql.org
Subject: Optimizer for IN (..) ? / Re: Thank you ! Re: Is there any Faster workaround ??
Date: Wed, 10 Apr 2002 12:24:26 +0200
Message-ID: <5.1.0.14.2.20020410122013.01cfdec0@pop.kundenserver.de> (raw)
In-Reply-To: <3CB35DF8.D26E2055@trade-india.com>
References: <3CB346F6.1DD7CFB9@trade-india.com>
	<3CB356D8.48F8F5F4@nsd.ca>

Hello,

At 09.04.2002 23:32, Rajesh Kumar Mallah <mallah@trade-india.com> wrote:
>i think this question has been answered before also in
>this mailing list  sorry for asking...
>...
> > How about:
> >
> > DELETE  from t_a where exist (select email from t_b where t_b.email =
> > t_a.email)
> >
> > Rajesh Kumar Mallah wrote:
> > > ... We require to do below or similar quite often
> > >
> > > DELETE  from t_a where email in (select email from t_b);
> > >
> > > everyone knows "IN" is pain fully slow currently in pgsql
> > > is the any fster alternative to above query

Yes this question was posted before - and if so, and if the answer is so 
simple - would it not make sense to implement this wisdom in the optimizer?
Regards
// Bernd vdB




Message-ID: <5.1.0.14.2.20020410122013.01cfdec0@pop.kundenserver.de>
Permalink:  ../5.1.0.14.2.20020410122013.01cfdec0@pop.kundenserver.de/
Also on:    postgresql.org/message-id/5.1.0.14.2.20020410122013.01cfdec0@pop.kundenserver.de

 · 

reply

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-sql@postgresql.org
  Cc: bvdb@asa.de
  Subject: Re: Optimizer for IN (..) ? / Re: Thank you ! Re: Is there any Faster workaround ??
  In-Reply-To: <5.1.0.14.2.20020410122013.01cfdec0@pop.kundenserver.de>

* 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