Re: plan difference between set-returning function with ROWS within IN() and a plain join

From: PFC <lists(at)peufeu(dot)com>
To: "Frank van Vugt" <ftm(dot)van(dot)vugt(at)foxi(dot)nl>, pgsql-performance(at)postgresql(dot)org
Subject: Re: plan difference between set-returning function with ROWS within IN() and a plain join
Date: 2008-05-06 09:53:17
Message-ID: op.uap8e3owcigqcu@apollo13.peufeu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, 06 May 2008 10:21:43 +0200, Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
wrote:

> L.S.
>
> I'm noticing a difference in planning between a join and an in() clause,
> before trying to create an independent test-case, I'd like to know if
> there's
> an obvious reason why this would be happening:

Is the function STABLE ?

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Vlad Arkhipov 2008-05-06 11:14:03 Seqscan problem
Previous Message Frank van Vugt 2008-05-06 08:21:43 plan difference between set-returning function with ROWS within IN() and a plain join