> There's been some talk about prohibiting flattening if there are any
> volatile functions in the subselect's targetlist, but nothing's been
> done about that. Disabling flattening is a sufficiently big hit to
> the planner's optimization ability that it shouldn't be done lightly.
>
> regards, tom lane
>
http://archives.postgresql.org/pgsql-hackers/2005-10/msg00396.php
maybe a guc?
is this worth trying? maybe it's fair to say is to late for 8.2 but
maybe it can be qeued for 8.3...
i think i can do this in 1 or 2 days...
BTW, can you think in a good name for a GUC for this?
--
regards,
Jaime Casanova
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
