On Apr 17, 2013, at 12:51 PM, Josh Berkus wrote:
>
>> "Postgres developers and users believe that quality view support is an
>> important toolset for any database, and Postgres 9.3 includes several
>> improvements to it's view support. Enhancements included in this
>> release include the ability to create recursive views, to create
>> automatically updateable views, and limited support for built in
>> materialized views."
>
> The purpose of advocacy, and release announcements, is to *promote*
> PostgreSQL, not to advertise every bug we have and every limitation.
> Nitpicky perfectionism may be useful when we're writing code, but it
> seriously undermines the project if it appears in our advocacy
> materials. What other open source DBMS even has the concept of
> materialized views?
I agree on that, but also on that note, we do have future opportunities to promote feature improvements as news. Once
wedo have full support for materialized views, that is still news, much like the JSON improvements are newsworthy in
9.3too, even though JSON support was released in 9.2.
New features are not limited to "one shot" of press. We should promote materialized views now knowing full well we can
alwayspromote them again later, even if it's something as simple as "new materialized views support" - it sounds like
it'sbrand new, even if it is just enhanced.
Jonathan
