Re: Postgresql Materialized views

From: tomas(at)tuxteam(dot)de
To: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>
Cc: 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sean Utt <sean(at)strateja(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgresql Materialized views
Date: 2008-01-14 14:09:10
Message-ID: 20080114140910.GA15438@www.trapp.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jan 14, 2008 at 07:28:52AM -0600, Roberts, Jon wrote:

[...]

> What happens when a person adds a feature or changes the architecture of the
> database that is perceived by some as incorrect or going in the wrong
> direction?

(S)he gets to hold onto her/his own version. If there is enough power
behind both variants, a fork might happen.

Forks are not bad per se -- on the contrary, the variants can explore
a wider area of design space. If they stay sufficiently open, they later
steal ideas (and even code) from each other. Think genetic algorithms on
a global scale ;-)

But now it's definitely off-topic, so I'll shut up already.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFHi20GBcgs9XrR2kYRAppzAJ0VSKzWb8jjEQfMCwW1ycpCAyEZUQCdFmtz
tDpywf0ywvk+3j0qI1GUHkI=
=3TME
-----END PGP SIGNATURE-----

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-01-14 14:20:17 Re: Postgresql Materialized views
Previous Message Mark Mielke 2008-01-14 14:07:54 Re: Postgresql Materialized views