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

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: PFC <lists(at)peufeu(dot)com>, 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 11:55:52
Message-ID: 200805061355.52654.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> > 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 ?

Yep.

For the record, even changing it to immutable doesn't make a difference in
performance here.

--
Best,

Frank.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeff 2008-05-06 12:26:03 Re: RAID 10 Benchmark with different I/O schedulers (was: Performance increase with elevator=deadline)
Previous Message Vlad Arkhipov 2008-05-06 11:14:03 Seqscan problem