On Tue, Jan 16, 2007 at 02:55:08PM -0700, Nathan Bell wrote:
> Yeah, I saw the "not optimized out" typo as soon as I hit send.
>
> What if the item that is taking a long time isn't a function, but rather
> a sub-select?

The planner should be able to see that the item is non-volatile itself.
It only needs to be told for functions because it can't see into them.

> Can I set the sub-select to stable, or perhaps set the entire view to
> non-volatile to achieve the same result?

No.

> If not, can I set the sub-select to a different non-volatile view or do
> I need to create a non-volatile function that returns the result?

You could create a function that does the job, but that's generally not
necessary.

Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFrUwHIB7bNG8LQkwRAuRuAJ9pnh6IIM99M+PPcVYdZW GNyYCxCgCfYsMN
tpNCFoTWOYJErv2cEPfNDqU=
=Xz3d
-----END PGP SIGNATURE-----