On Sat, Oct 4, 2008 at 5:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> that Oracle chooses to treat WITH-queries as if they were plain
> sub-selects if they're non-recursive and only referenced once.
> That is, Oracle would rewrite the above into
>
>        SELECT * FROM ( SELECT * FROM foo ) AS q WHERE key = 42;
>
> and then flatten the sub-select and optimize normally.  It would
> not be hard to make Postgres do the same, but then we would lose
> some guarantees about predictable execution of volatile functions.
>
[...]
>
> Any thoughts on what to do?  One possibility is to flatten only
> if the subquery doesn't contain any volatile functions.
>

maybe i'm missing something but AFAIR postgres will not try to
optimize (push down/pull up) if it see any volatile function.

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

• Common Table Expressions applied; some issues remain at 2008-10-04 22:22:23 from Tom Lane

pgsql-hackers by date

Next:	From: Tatsuo Ishii	Date: 2008-10-04 23:44:36
	Subject: Re: Common Table Expressions applied; some issues remain
Previous:	From: Tom Lane	Date: 2008-10-04 22:39:49
	Subject: Re: Obsolete functions istrue, isfalse, etc.