From: Frank van Vugt <ftm.van.vugt@foxi.nl>
To: PFC <lists@peufeu.com>
To: pgsql-performance@postgresql.org
Subject: Re: plan difference between set-returning function with ROWS within IN() and a plain join
Date: Tue, 6 May 2008 13:55:52 +0200
Message-ID: <200805061355.52654.ftm.van.vugt@foxi.nl> (raw)
In-Reply-To: <op.uap8e3owcigqcu@apollo13.peufeu.com>
References: <200805061021.43448.ftm.van.vugt@foxi.nl>
<op.uap8e3owcigqcu@apollo13.peufeu.com>
> > 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.
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-performance@postgresql.org
Cc: ftm.van.vugt@foxi.nl, lists@peufeu.com
Subject: Re: plan difference between set-returning function with ROWS within IN() and a plain join
In-Reply-To: <200805061355.52654.ftm.van.vugt@foxi.nl>
* 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