Robert Treat wrote: > ISTM the allure of differentiation and branding is going to be too strong for > us to prevent such things. An easy way to differentiate is to add some > proprietary/unique extension to the main code and then package that up. If > you have to have all your extensions be put into the community version then > lose this advantage over your comptetitors. (Mammoth PostgreSQL/Replicator is > an example of this) The same holds true for branding.... if your Pervasive > you want to sell Pervasive Postgres rather than PostgreSQL because you get to > push your name out there, and get people thinking about your company whenever > they talk about the database. > > I think our goal is to encorage companies to push these changes into the core > as much as possible, pointing out things like the advantages community > support brings like ongoing maintainance, support in add-on tools like > pgadmin or phppgadmin, and eliminating the chance that someone else will > submit a similar solution that gets accepted to the community code there by > deprecating the work they have already done.
I remember something the president of Great Bridge told me, he said, "Great Bridge needs PostgreSQL. If Great Bridge dies, PostgreSQL goes on (as it did), but if PostgreSQL dies, Great Bridge is dead too". -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
