Fantastic, I was planning on a bit of materialized view investigations myselfYou can view my summary at http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html
Comments and suggestions are definitely welcome.
when time permits, I'm pleased to see you've started the ball rolling.
I was thinking about your problem with mutable functions used in a materialized view.
How about eliminating the mutable functions as much as possible from the underlying
view definition, and create another view on top of the materialized view that has the mutable bits!
Giving you the best of both worlds.
I haven't tried this or thought it through very much - too busy - but I'd thought I'd throw
it in for a bit o' head scratching, and chin stroking :)
Cheers -- Mark Gibson <gibsonm |AT| cromwell |DOT| co |DOT| uk> Web Developer & Database Admin Cromwell Tools Ltd. Leicester, England.
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
