On lör, 2011-02-05 at 12:26 +0100, Nick Rudnick wrote: > o extensions of PostgreSQL to support such a kind of usage have to > be expected to be expected to be rejected from integration to the code > base core -- i.e., if they are done, students have to be told «you > can't expect this to become a part of PostgreSQL»
There are very varied interests in this community. But you have to keep in mind that PostgreSQL is a production software package, not a research platform. This doesn't mean that we discourage research with the PostgreSQL code base. But that should be done in a fork. Code aimed for inclusion in a proper PostgreSQL release should have demonstrable real life use and should be developed according to certain standards and in close corporation with the community. If a research project can deal with that, great, but typically, research projects are there to determine whether something could have real-life value in the first place, and development follows different standards of quality. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
