Re: ANTI-JOIN needs table, index scan not possible?

From: Kenneth Marshall <ktm(at)rice(dot)edu>
To: hans wulf <lotu1(at)gmx(dot)net>
Cc: Maciek Sakrejda <msakrejda(at)truviso(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: ANTI-JOIN needs table, index scan not possible?
Date: 2011-03-11 22:16:03
Message-ID: 20110311221603.GI8169@aart.is.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Mar 11, 2011 at 06:54:39PM +0100, hans wulf wrote:
> Thanks for the answer.
>
> so there's no way around this problem? A nice index bitmap merge thing would be super fast. Big table ANTI JOIN queries with only a few results expected, are totally broken, if this is true.
>
> This way the query breaks my neck. This is a massive downside of postgres which makes this kind of query impossible. Mysql gives you the answer in a few seconds :-(
>
>

Super! I am glad that MySQL can meet your needs. No software is
perfect and you should definitely chose based on your use-case.

Regards,
Ken

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2011-03-11 22:32:03 Re: ANTI-JOIN needs table, index scan not possible?
Previous Message fork 2011-03-11 19:06:39 Re: Tuning massive UPDATES and GROUP BY's?