Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> There was some talk awhile ago of preventing flattening when the
> subquery targetlist contains volatile functions, but we didn't
> have any consensus that the cure would be better than the disease.
> (In particular, since user-defined functions default to being
> considered volatile, such a restriction could easily cripple
> optimization of subqueries.)
Thinking aloud... Postgres could have a VOLATILE function attribute to
explicitly mark functions requiring special care.
The default could be sort of a best-guess
Perhaps eventually warning on functions created without being explicitly
Well, I guess Postgres can't warn on a valid SQL function if it's interested
in spec conformance. But it could be an option to do so.
In response to
pgsql-general by date
|Next:||From: Michael Fuhr||Date: 2004-11-29 06:43:28|
|Subject: Re: How many views...|
|Previous:||From: Shachar Shemesh||Date: 2004-11-29 04:41:09|
|Subject: Re: sequencing two tables|