Re: Postgresql Materialized views

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> My point is simply this: The lack of a clear formal process for feature 
> requests leads to this degradation in the conversation. Without a formalized 
> structure, the conversation devolves rapidly into an argument over semantics 
> and word choice.
...
> There needs to be a way to evaluate the demand for a specific feature as 
> well as the benefits and the effort it will require.

You could always start a page on the developer's wiki:

http://developer.postgresql.org/

That would seem to be a good place to at least describe the problem in detail, 
show how you would like a feature to behave, and have people add the pros and 
cons of certain approaches. Certainly would be better to have a page to point 
to rather than trying to trawl through mailing archives (heck, the page could 
even mostly be a collection of such links).

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200801141104
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iD8DBQFHi4gvvJuQZxSWSsgRA66dAKCGCPBPDfTFDoizE0WDwXBzDK/W3ACg8dwZ
99OvuSU9PPmG6XDPPK2iQzA=
=Xseg
-----END PGP SIGNATURE-----