Re: Query too slow with "not in" condition [Resolved]

From: சிவகுமார் மா <masivakumar(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Query too slow with "not in" condition [Resolved]
Date: 2008-12-01 07:21:57
Message-ID: 139e14f00811302321l4bf3f8efuef87dc8719c89b24@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks a lot.

On Sun, Nov 30, 2008 at 11:28 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David Rowley" <dgrowley(at)gmail(dot)com> writes:
> > I assume workmem, effective_cache_size and random_page_cost are all the
> same
> > in the 2 postgresql.conf?
>
> Indeed, work_mem is probably the problem. The critical difference
> between the two plans seems to be that the first one is using a
> "hashed subplan" and the second one isn't. Assuming the same datatypes in
> both databases, the only reason not to use a hashed subplan is if the
> hashtable is estimated not to fit in work_mem.
>

I changed work_mem in test machine to be implemented in production server
later. Completely forgot that when faced with this issue. Sorry for the
trouble.

I learnt about "hashed subplan" requiring sufficient work_mem, however.

Thanks and regards,

Ma Sivakumar

மா சிவகுமார்
எல்லோரும் எல்லாமும் பெற வேண்டும்
http://masivakumar.blogspot.com

Browse pgsql-general by date

  From Date Subject
Next Message சிவகுமார் மா 2008-12-01 07:23:31 Re: Query too slow with "not in" condition
Previous Message Stéphane A. Schildknecht 2008-12-01 07:18:12 Re: Trigger before delete does fire before, but delete doesn't not happen