Thread: Postgres article
Well, Postgres only got ONE LINE in this article, but at least it got a mention. But the line that got me laughing was: "There are a few open source databases out there," Aberdeen Group research director Bill Claybrook told NewsFactor. "[But]if you look at the functionality between MySQL and Oracle 9i, there are some big differences." No offense to the MySQL people, but a fairer comparison is MySQL vs. Access and Postgres vs. Oracle. http://www.newsfactor.com/perl/printer/19752/ -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze
Ted, > http://www.newsfactor.com/perl/printer/19752/ I posted the following using their online response form. Reporters are usually glad to augment their future articles if you point them to a souce of information. The article probably only covered MySQL because that's the only OS database that anyone at NewsFactor knew anything about. More that that, this article points out the reason that we need press releases. My letter below. "Editors, I appreciated Ms. Lyman's recent article on Open Source databases. It's gratifying to see the business press paying more attention to the alternatives to expensive proprietary databases. However, I feel that the article focused a bit too much on MySQL to the exclusion of all other Open Source databases. You are probably not aware that PostgreSQL, SAP DB, and Phoenix all have substantial installed user bases, and offer quite a range of features for different users. Particularly, the comparison of Oracle with MySQL is a bit uninformed. MySQL was designed to be a "lightweight" and fast database, and not to compete with Oracle. PostgreSQL and SAP DB are much more comparable to Oracle in their features and scalability. This sort of comparison does a disservice, both to MySQL and to the other Open Source databases. I realize that information on Open Source software can often be hard to find, and difficult to understand. That's why the PostgreSQL advocacy team, led by Justin Clift (justin@postgresql.org), put up this site for PostgreSQL information: http://advocacy.postgresql.org Please feel free to contact the advocacy team if you need information on PostgreSQL for future articles. Thanks for your attention, Josh Berkus Volunteer, PostgreSQL Project"
> More that that, this article points out the reason that we need press > releases. I have a list of several hundred magazine and publication editors and such that I use for sending out PgSQL related press releases ... Justin and I have already discussed doing up a strong press release for this release as well and making sure that that gets out to the list ...
Excellent work guys. Josh's letter can serve as a sort of template for sending in to editors. Marc sounds like you are ready to bring out the big guns! ----- Original Message ----- From: "Marc G. Fournier" <scrappy@hub.org> Date: Thu, 24 Oct 2002 09:04:21 -0300 (ADT) To: Josh Berkus <josh@agliodbs.com> Subject: Re: [pgsql-advocacy] Postgres article > > > More that that, this article points out the reason that we need press > > releases. > > I have a list of several hundred magazine and publication editors and such > that I use for sending out PgSQL related press releases ... Justin and I > have already discussed doing up a strong press release for this release as > well and making sure that that gets out to the list ... > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > > -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze
Marc, > I have a list of several hundred magazine and publication editors and > such > that I use for sending out PgSQL related press releases ... Justin > and I > have already discussed doing up a strong press release for this > release as > well and making sure that that gets out to the list ... Cool. I also have the press list from Linux World Expo ... want it in case you can add a few people? I strongly reccommend that we start working on the press release *now*. PRs have a tendancy to require 14 drafts, and then we'll want to get it translated by our non-English-language volunteers to hit as much of the foriegn-language press as we can. While we're at it, can we creat a press@postgresql.org alias that funnels to Justin, Bruce, etc.? It'd be nice to have an address to give out. -Josh Berkus
the archives for pgsql advocacy are not available on the website. jeff.
Ted, > Excellent work guys. Josh's letter can serve as a sort of > template for sending in to editors. Thank you. HOWEVER, it's very, very important to remember that reporters are *individuals*. I would *not* have written such an impersonal letter to, for example, Steven Shankland or Peter Gallipoli, both of whom are easy to approach informally. (Please note ... the following is my opinion for discussion, I'm not in charge of PR, Justin is) I did that letter as an example ... since NewsFactor is a minor publication, anyway ... but in the future we'll need to handle things in a more organized manner. Whenever there is an article to respond to, we should post it and poll this list to see if anyone has a personal relationship with the reporter, and then our fearless leader (Justin) can decide who should contact the reporter or editor. Also keep in mind that the archives of this list are *public*, and we have to be careful what we say about reporters and publications in our e-mail. I've already had the bitter experience of having to kiss up to a reporter for a week to make up for a careless statement on marketing@openoffice.org ... -Josh Berkus
Josh Berkus wrote: <snip> > > While we're at it, can we creat a press@postgresql.org alias that > funnels to Justin, Bruce, etc.? It'd be nice to have an address to > give out. Hey, now that's a really cool idea. Marc, are you ok to arrange this? :-) Regards and best wishes, Justin Clift > -Josh Berkus > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
"Marc G. Fournier" wrote: <snip> > I have a list of several hundred magazine and publication editors and such > that I use for sending out PgSQL related press releases ... Justin and I > have already discussed doing up a strong press release for this release as > well and making sure that that gets out to the list ... Perhaps it's worthwhile looking at the press releases created for OpenOffice.org and follow that format, or we could also take a look at other guidelines. For example: http://www.vergenet.net/~conrad/linux/pr Thoughts? :-) Regards and best wishes, Justin Clift -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
On Thu, 24 Oct 2002, Josh Berkus wrote: > Marc, > > > I have a list of several hundred magazine and publication editors and > > such > > that I use for sending out PgSQL related press releases ... Justin > > and I > > have already discussed doing up a strong press release for this > > release as > > well and making sure that that gets out to the list ... > > Cool. I also have the press list from Linux World Expo ... want it in > case you can add a few people? Yes, please ... > I strongly reccommend that we start working on the press release *now*. Already in the works, we hope to have 1st draft by end of the weekend, if not sooner ... > PRs have a tendancy to require 14 drafts, and then we'll want to get > it translated by our non-English-language volunteers to hit as much of > the foriegn-language press as we can. Thought about that one too :)
Marc,
> > I strongly reccommend that we start working on the press release
> *now*.
>
> Already in the works, we hope to have 1st draft by end of the
> weekend, if
> not sooner ...
Want my help, or are there already "too many cooks"?
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
On Thu, 24 Oct 2002, Josh Berkus wrote: > Marc, > > > > I strongly reccommend that we start working on the press release > > *now*. > > > > Already in the works, we hope to have 1st draft by end of the > > weekend, if > > not sooner ... > > Want my help, or are there already "too many cooks"? Geoff is doing up a PR from the 'sales and marketing' perspective, and once done, we'll put it around for comments and additions ... basically, the man, IMHO, can write so well that he can make you feel good for being called an idiot ... I've given him everything I can think of to start the 1st Draft, but I'm bound to have missed something :) Give us a couple of days ...
Marc G. Fournier wrote:<br /><blockquote cite="mid20021024090141.B15744-100000@hub.org" type="cite"><blockquote type="cite"><prewrap="">More that that, this article points out the reason that we need press releases. </pre></blockquote><pre wrap=""> I have a list of several hundred magazine and publication editors and such that I use for sending out PgSQL related press releases ... Justin and I have already discussed doing up a strong press release for this release as well and making sure that that gets out to the list ... </pre></blockquote> I can get a few email addresses of brazilian editors and magazines, if it will help...<br /><br /><preclass="moz-signature" cols="$mailwrapcol">-- Diogo de Oliveira Biazus <a class="moz-txt-link-abbreviated" href="mailto:diogo@ikono.com.br">diogo@ikono.com.br</a> Ikono Sistemas e Automação <a class="moz-txt-link-freetext" href="http://www.ikono.com.br">http://www.ikono.com.br</a> </pre>
Good morning!
As requested, I've put together a draft proposal for this announcement
of the upcoming release.
This is clearly done with an advocacy based sales & marketing spin. It
follows sales.org's proven 6 'Power Opening©' steps (of course):
1. Who you are (PGDG)
2. What you're selling (PostgreSQL)
3. What's In It for Them (free alternative to commercial solutions)
4. Why should they believe you (third party quotes/endorsements)
5. Expectations (changes in this release, making it even better!)
6. Process (Where to go and get the code or more info)
Feel free to change and improve any of the content as you wish, I'm
not burdened by any ego issues wrt pride in authorship, even if you
decide to throw it out and start over ;)
--Geoff
-----
For Immediate Release November 1st, 2002
PostgreSQL Global Development Group Announces Version 7.3
PostgreSQL, the world's most advanced open source database,
provides solutions for many of the most demanding applications in
use today, saving business and government millions of dollars each
year. The PostgreSQL Global Development Group proudly announces that
the "best is better again" with the release of the freely available
PostgreSQL v7.3 object-relational database management system (ORDBMS).
With more than 16 years of development by hundreds of the
world's most generous and brilliant minds from the open source
community, PostgreSQL continues to make the decision between free
software and commercial databases "a simple choice between open source
or an open wallet." Many companies and agencies can no longer afford
the high costs and constantly changing terms of licensed commercial
software - making PostgreSQL one of the most highly sought after free
technologies in the market today. With the release of v7.3 the
decision to choose PostgreSQL will be even easier.
Here is what some current PostgreSQL users have gone on record
to say about this technology:
"We believe that the key point relating to databases for the
.ORG redelegation is not which database the operator is using, but,
rather, whether the database will support the .ORG registry in a
stable, scalable, and highly available manner.
...over a year of experience...clearly demonstrates that the
PostgreSQL database used by Afilias performs at the level of
reliability and availability required for the mission critical
operations of a global gTLD registry."
Internet Society (ISOC)
"PostgreSQL has scaled perfectly with our rapidly expanding
business, and we recommend it over every other DB."
TrustCommerce, California
"PgMarket has been developed around PostgreSQL because of its
unmatched performance, features, price, and scalability. It is the best
possible database for enterprise e-commerce."
Fitcom srl, Italy
"PostgreSQL provided sales.org with a solution that was $70,000
less expensive to create, and over 70% lower in cost to operate and
maintain than any of the commercial DBMS offerings we looked at."
sales.org Inc., Toronto
"PostgreSQL handles virtually all the standard SQL constructs.
It is easy (relatively speaking) to administer, it is fast, it is
efficient, it has a great API, and it supports ODBC, why would you
choose something else?"
Mohawk Software, Massachusetts
"... selected PostgreSQL as one of the key components for their
solution, relying on the power and extensibility of the database even
under heavy load."
Vanten, K.K., Tokyo
Additions & improvements in Version 7.3 release include:
SCHEMAS
Schemas allow users to create objects in their own namespace
so two people or applications can have tables with the same
name. There is also a public schema for shared tables.
Table/index creation can be restricted by removing
permissions on the public schema
Drop Column
Now supports ALTER TABLE ... DROP COLUMN functionality.
Table Functions
Functions returning multiple rows and/or multiple columns are
now much easier to use than before. The "table function" can
be called in the SELECT FROM clause, treating its output like
a table. Also, plpgsql functions can now return sets.
Prepared Queries
For performance, PostgreSQL now supports prepared queries.
Dependency Tracking
PostgreSQL now records object dependencies, which allows
improvements in many areas.
Privileges
Functions & procedural languages now have privileges. People
running these can take on the privileges of their creators.
Multibyte/Locale
Both multibyte and locale are now always enabled.
Logging
A variety of logging options have been enhanced.
Interfaces
A large number of interfaces have been moved to
http://gborg.postgresql.org where they can be developed
and released independently.
Functions/Identifiers
By default, functions can now take up to 32 parameters, and
identifiers can be up to 63 bytes long.
Along with many many more enhancements, bug fixes and
performance related changes from v7.2 ...
Source for this release is available on all mirrors under:
/pub/source/v7.3
More information on PostgreSQL is available on the project
websites mirrored worldwide through:
http://www.postgresql.org
A complete list of changes in v7.3 can be found in the HISTORY
file, included with the release, or available from all ftp mirrors as:
/pub/README.v7_3
Marc G. Fournier
Co-ordinator
PostgreSQL Global Development Group
Geoff, > As requested, I've put together a draft proposal for this > announcement > of the upcoming release. Hmmm ... this release reads like a "We know you've never heard of PostgreSQL before, so here's some great stuff about PostgreSQL, and by the way, we have a new release." Which is OK if we believe that most of our press targets are, in fact, completely ignorant of PostgreSQL. I think, though, that we are most likely to get coverage from the OS-freindly press, who *are* aware of PostgreSQL. Thues, we may want to consider an approach that focuses more on the new release and less on PostgreSQL as a whole. The PostgreSQL-as-a-whole stuff can be linked on the PostgreSQL Advocacy Web Site, which is where we should put most of the quotes, anyway. We also need to explain about the new features: a) Why this feature is important in plain english; b) How this feature makes us equal to/better than other enterprise databases c) ... but craft the language to make sure that we don't imply that PostgreSQL was somehow inferiour before. Finally, we need a list of press contacts, with e-mail, phone, and snail-mail addresses -- preferably one on each continent. And we shouldn't link to the main postgreSQL site, with is *not* set up for Press access. -Josh Berkus > For Immediate Release November 1st, > 2002 > > PostgreSQL Global Development Group Announces Version 7.3 > > PostgreSQL, the world's most advanced open source database, > provides solutions for many of the most demanding applications in > use today, saving business and government millions of dollars each > year. The PostgreSQL Global Development Group proudly announces that > the "best is better again" with the release of the freely available > PostgreSQL v7.3 object-relational database management system > (ORDBMS). > > With more than 16 years of development by hundreds of the > world's most generous and brilliant minds from the open source > community, PostgreSQL continues to make the decision between free > software and commercial databases "a simple choice between open > source > or an open wallet." Many companies and agencies can no longer afford > the high costs and constantly changing terms of licensed commercial > software - making PostgreSQL one of the most highly sought after free > technologies in the market today. With the release of v7.3 the > decision to choose PostgreSQL will be even easier. > > Here is what some current PostgreSQL users have gone on > record > to say about this technology: > > "We believe that the key point relating to databases for the > .ORG redelegation is not which database the operator is using, but, > rather, whether the database will support the .ORG registry in a > stable, scalable, and highly available manner. > ...over a year of experience...clearly demonstrates that the > PostgreSQL database used by Afilias performs at the level of > reliability and availability required for the mission critical > operations of a global gTLD registry." > Internet Society (ISOC) > > "PostgreSQL has scaled perfectly with our rapidly expanding > business, and we recommend it over every other DB." > TrustCommerce, California > > "PgMarket has been developed around PostgreSQL because of its > unmatched performance, features, price, and scalability. It is the > best > possible database for enterprise e-commerce." > Fitcom srl, Italy > > "PostgreSQL provided sales.org with a solution that was > $70,000 > less expensive to create, and over 70% lower in cost to operate and > maintain than any of the commercial DBMS offerings we looked at." > sales.org Inc., Toronto > > "PostgreSQL handles virtually all the standard SQL > constructs. > It is easy (relatively speaking) to administer, it is fast, it is > efficient, it has a great API, and it supports ODBC, why would you > choose something else?" > Mohawk Software, Massachusetts > > "... selected PostgreSQL as one of the key components for their > solution, relying on the power and extensibility of the database even > > under heavy load." > Vanten, K.K., Tokyo > > > Additions & improvements in Version 7.3 release include: > > SCHEMAS > Schemas allow users to create objects in their own namespace > so two people or applications can have tables with the same > name. There is also a public schema for shared tables. > Table/index creation can be restricted by removing > permissions on the public schema > > Drop Column > Now supports ALTER TABLE ... DROP COLUMN functionality. > > Table Functions > Functions returning multiple rows and/or multiple columns are > now much easier to use than before. The "table function" can > be called in the SELECT FROM clause, treating its output like > a table. Also, plpgsql functions can now return sets. > > Prepared Queries > For performance, PostgreSQL now supports prepared queries. > > Dependency Tracking > PostgreSQL now records object dependencies, which allows > improvements in many areas. > > Privileges > Functions & procedural languages now have privileges. People > running these can take on the privileges of their creators. > > Multibyte/Locale > Both multibyte and locale are now always enabled. > > Logging > A variety of logging options have been enhanced. > > Interfaces > A large number of interfaces have been moved to > http://gborg.postgresql.org where they can be developed > and released independently. > > Functions/Identifiers > By default, functions can now take up to 32 parameters, and > identifiers can be up to 63 bytes long. > > Along with many many more enhancements, bug fixes and > performance related changes from v7.2 ... > > Source for this release is available on all mirrors under: > /pub/source/v7.3 > > More information on PostgreSQL is available on the project > websites mirrored worldwide through: > http://www.postgresql.org > > A complete list of changes in v7.3 can be found in the > HISTORY > file, included with the release, or available from all ftp mirrors > as: > /pub/README.v7_3 > > Marc G. Fournier > Co-ordinator > PostgreSQL Global Development Group > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco
Folks, Oh, and one more thing: we should have at least one quote from a core developer on why the new features for the new release are great. -Josh
Wow Josh, that's a bunch of assumptions I wouldn't make. Heck, even most of the OS companies that bundle postgresql are clueless about it, and they're way ahead of the CIO/CTO readers that I was aiming this at, based on what the media have asked us to provide them with in news items we have on postgresql... Marc, as this is a press release for the community, not PostgreSQL, Inc., it seems I may have wasted everyone's time by missing the intended audience, which wasn't my intention... I apologize for missing the mark after the *huge* buildup you gave about me doing up this draft. As I said, ( - no harm, no foul :) ... "even if you decide to throw it out and start over ;)" It sounds like Josh is very clear on this needing to be targeted for a much more familiar and sophisticated media audience than I know, so hopefully he'll put the right message together and let the PGDG group adjust it to language and focus that is suitable. I can't speak much to the media list, we've got our own internal list at PgSQL, Inc. which consists primarily of journalists, publications, individuals and companies that have asked us to provide them with information. It isn't appropriate for us to breach their privacy by releasing that list publicly (and none of our maillists are for sale or rent, ever), but we'll distribute whatever PGDG comes up with, to ensure that everyone we know who's interested hears about the new release. Josh, you apparently have a much different set of media people you're talking with, so I'd encourage you to collaborate with Justin, Bill Pollock and others to help compile an internal PGDG media / press list that will be specific to the needs and goals of the postgresql community. As always, best regards, --Geoff > Josh Berkus wrote: > > Geoff, > > > As requested, I've put together a draft proposal for this > > announcement of the upcoming release. > > Hmmm ... this release reads like a "We know you've never heard of > PostgreSQL before, so here's some great stuff about PostgreSQL, and by > the way, we have a new release." Which is OK if we believe that most > of our press targets are, in fact, completely ignorant of PostgreSQL. > > I think, though, that we are most likely to get coverage from the > OS-freindly press, who *are* aware of PostgreSQL. Thues, we may want > to consider an approach that focuses more on the new release and less > on PostgreSQL as a whole. The PostgreSQL-as-a-whole stuff can be > linked on the PostgreSQL Advocacy Web Site, which is where we should > put most of the quotes, anyway. > > We also need to explain about the new features: > a) Why this feature is important in plain english; > b) How this feature makes us equal to/better than other enterprise > databases > c) ... but craft the language to make sure that we don't imply that > PostgreSQL was somehow inferiour before. > > Finally, we need a list of press contacts, with e-mail, phone, and > snail-mail addresses -- preferably one on each continent. And we > shouldn't link to the main postgreSQL site, with is *not* set up for > Press access. > > -Josh Berkus
Geoff, > Wow Josh, that's a bunch of assumptions I wouldn't make. > Heck, even most of the OS companies that bundle postgresql are > clueless about it, and they're way ahead of the CIO/CTO readers > that I was aiming this at, based on what the media have asked > us to provide them with in news items we have on postgresql... Hey, my opinions are for discussion. That's why I posted them before starting a re-write. What do other people think? Justin? > Marc, as this is a press release for the community, not > PostgreSQL, Inc., it seems I may have wasted everyone's time > by missing the intended audience, which wasn't my intention... > I apologize for missing the mark after the *huge* buildup you > gave about me doing up this draft. Maybe *I* made a mistaken assumption. I assumed that we were working on a press release for the general tech press. Do we have other press releases to do? > As I said, ( - no harm, no foul :) ... "even if you decide to > throw it out and start over ;)" Yeah. Personal pride has no place in a press release ... mine on OOo have been cut to ribbons, more than once. > It sounds like Josh is very clear on this needing to be targeted > for a much more familiar and sophisticated media audience than I > know, so hopefully he'll put the right message together and let > the PGDG group adjust it to language and focus that is suitable. Whoa! Let's hash this out first. For one thing, Justin is Lead for Advocacy, not me ... I was just stating my opinion. > Josh, you apparently have a much different set of media people > you're talking with, so I'd encourage you to collaborate with > Justin, Bill Pollock and others to help compile an internal > PGDG media / press list that will be specific to the needs and > goals of the postgresql community. Yeah, I still need to sort that out. I have: 1) The media people I personally know (Roblimo, Stephen, Noah); 2) The list from Linux World Expo; 3) The OpenOffice.org press list Obviously, I can't use list (3) from PostgreSQL without official permission, and I'm still sorting out who is in groups 1) and 2). -Josh Berkus
Geoff, Well done, I think this is great. Minor copy tweaks, suggestions only, hopefully not too pedantic: --======-- In this passage, "again" connotes that it wasn't good for a while there or something: From: proudly announces that the "best is better again" To: proudly announces that "The best has gotten even better!" --======-- The phrase "decision to choose" sounds off to me: From: With the release of v7.3 the decision to choose PostgreSQL To: With the release of v7.3 the decision to adopt PostgreSQL Or: With the release of v7.3 the decision to use PostgreSQL Or: With the release of v7.3 the decision to try PostgreSQL --======-- If we do pare back the # of quotes in this release (saving ammo for future releases can't hurt) I'd keep the Afilias one and narrow the first sentence thusly: From: We believe that the key point relating to databases for the .ORG redelegation is not which database the operator is using, but, rather, whether the database will support the .ORG registry in a stable, scalable, and highly available manner. To: We believe that the key point relating to databases for the .ORG redelegation is... whether the database will support the .ORG registry in a stable, scalable, and highly available manner. --======-- That's all I see for now... Thanks, Shane McChesney President, Wesearch Information Services Inc. Site: http://www.wesearchis.com Weblog: http://www.skippingdot.net On Sun, 27 Oct 2002 10:13:21 -0500, Geoff Davidson wrote: >Good morning! > >As requested, I've put together a draft proposal for this >announcement of the upcoming release. > >This is clearly done with an advocacy based sales & marketing spin. >It follows sales.org's proven 6 'Power Opening©' steps (of course): >1. Who you are (PGDG) >2. What you're selling (PostgreSQL) >3. What's In It for Them (free alternative to commercial solutions) >4. Why should they believe you (third party quotes/endorsements) >5. Expectations (changes in this release, making it even better!) >6. Process (Where to go and get the code or more info) > >Feel free to change and improve any of the content as you wish, I'm >not burdened by any ego issues wrt pride in authorship, even if you >decide to throw it out and start over ;) > >--Geoff > >----- > >For Immediate Release November 1st, >2002 > >PostgreSQL Global Development Group Announces Version 7.3 > >PostgreSQL, the world's most advanced open source database, provides >solutions for many of the most demanding applications in use today, >saving business and government millions of dollars each year. The >PostgreSQL Global Development Group proudly announces that the "best >is better again" with the release of the freely available PostgreSQL >v7.3 object-relational database management system (ORDBMS). > >With more than 16 years of development by hundreds of the world's >most generous and brilliant minds from the open source community, >PostgreSQL continues to make the decision between free software and >commercial databases "a simple choice between open source or an open >wallet." Many companies and agencies can no longer afford the high >costs and constantly changing terms of licensed commercial software >- making PostgreSQL one of the most highly sought after free >technologies in the market today. With the release of v7.3 the >decision to choose PostgreSQL will be even easier. > >Here is what some current PostgreSQL users have gone on record to >say about this technology: > >"We believe that the key point relating to databases for the .ORG >redelegation is not which database the operator is using, but, >rather, whether the database will support the .ORG registry in a >stable, scalable, and highly available manner. >...over a year of experience...clearly demonstrates that the >PostgreSQL database used by Afilias performs at the level of >reliability and availability required for the mission critical >operations of a global gTLD registry." Internet Society (ISOC) > >"PostgreSQL has scaled perfectly with our rapidly expanding >business, and we recommend it over every other DB." TrustCommerce, >California > >"PgMarket has been developed around PostgreSQL because of its >unmatched performance, features, price, and scalability. It is the >best possible database for enterprise e-commerce." Fitcom srl, Italy > "PostgreSQL provided sales.org with a solution that was $70,000 >less expensive to create, and over 70% lower in cost to operate and >maintain than any of the commercial DBMS offerings we looked at." >sales.org Inc., Toronto > >"PostgreSQL handles virtually all the standard SQL constructs. > >It is easy (relatively speaking) to administer, it is fast, it is >efficient, it has a great API, and it supports ODBC, why would you >choose something else?" Mohawk Software, Massachusetts > >"... selected PostgreSQL as one of the key components for their >solution, relying on the power and extensibility of the database >even under heavy load." Vanten, K.K., Tokyo > > >Additions & improvements in Version 7.3 release include: > >SCHEMAS Schemas allow users to create objects in their own namespace >so two people or applications can have tables with the same name. >There is also a public schema for shared tables. >Table/index creation can be restricted by removing permissions on >the public schema > >Drop Column Now supports ALTER TABLE ... DROP COLUMN functionality. > >Table Functions Functions returning multiple rows and/or multiple >columns are now much easier to use than before. The "table function" >can be called in the SELECT FROM clause, treating its output like a >table. Also, plpgsql functions can now return sets. > >Prepared Queries For performance, PostgreSQL now supports prepared >queries. > >Dependency Tracking PostgreSQL now records object dependencies, >which allows improvements in many areas. > >Privileges Functions & procedural languages now have privileges. >People running these can take on the privileges of their creators. > >Multibyte/Locale Both multibyte and locale are now always enabled. > >Logging A variety of logging options have been enhanced. > >Interfaces A large number of interfaces have been moved to >http://gborg.postgresql.org where they can be developed and released >independently. > >Functions/Identifiers By default, functions can now take up to 32 >parameters, and identifiers can be up to 63 bytes long. > >Along with many many more enhancements, bug fixes and performance >related changes from v7.2 ... > >Source for this release is available on all mirrors under: >/pub/source/v7.3 > >More information on PostgreSQL is available on the project websites >mirrored worldwide through: http://www.postgresql.org > >A complete list of changes in v7.3 can be found in the HISTORY > >file, included with the release, or available from all ftp mirrors >as: /pub/README.v7_3 > >Marc G. Fournier Co-ordinator PostgreSQL Global Development Group > >---------------------------(end of broadcast) >------------------------ >--- >TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/users-lounge/docs/faq.html
On Sun, 27 Oct 2002, Josh Berkus wrote: > > Marc, as this is a press release for the community, not > > PostgreSQL, Inc., it seems I may have wasted everyone's time > > by missing the intended audience, which wasn't my intention... > > I apologize for missing the mark after the *huge* buildup you > > gave about me doing up this draft. > > Maybe *I* made a mistaken assumption. I assumed that we were working > on a press release for the general tech press. Do we have other press > releases to do? IMHO, its the non-tech press that needs to be "informed/targetted" ... its alot easier on the techs if their CTO comes to them and mentioned 'this RDBMS PostgreSQL that they just read abou that we should investigate', then for the tech to convince the CTO ... eaiser to implement something when the higher-ups are pushing for it :)
Shane, thank you - those are great catches and suggestions. Josh Berkus raised some serious concerns about the focus, so there are some larger decisions on whether it should go forward in this form with some additions and changes that will help it with the press that he knows, or if it needs to go through a major rewrite - but your observations are very relevant for either direction. How about: Version 7.3 improvements make the choice of PostgreSQL an even easier decision. (my objective for that sentence is to acknowledge there are other 'choices', but really only one intelligent 'decision'...) I really like the change you suggested wrt the ISOC quote, less is often more. Justin has done a remarkable job in chasing down companies who are willing to confirm their choice of PostgreSQL, so we've got much more ammunition - I picked this selection because collectively it supports the business case for PostgreSQL on performance, price, scalability, complexity, usability, international installed base, and diversity of applications supported. There is an abundance of advice and disagreement on the length that a good release should be, to get maximum attention and exposure. I've found that a word count between 500 and 800 is usually effective. This one is in the 650 to 700 word range. --Geoff > Shane McChesney wrote: > > Geoff, > > Well done, I think this is great. > > Minor copy tweaks, suggestions only, hopefully not too pedantic: > > --======-- > > In this passage, "again" connotes that it wasn't good for a while > there or something: > > From: > proudly announces that the "best is better again" > To: > proudly announces that "The best has gotten even better!" > > --======-- > > The phrase "decision to choose" sounds off to me: > > From: > With the release of v7.3 the decision to choose PostgreSQL > To: > With the release of v7.3 the decision to adopt PostgreSQL > Or: > With the release of v7.3 the decision to use PostgreSQL > Or: > With the release of v7.3 the decision to try PostgreSQL > > --======-- > > If we do pare back the # of quotes in this release (saving ammo for > future releases can't hurt) I'd keep the Afilias one and narrow the > first sentence thusly: > > From: > We believe that the key point relating to databases for the .ORG > redelegation is not which database the operator is using, but, > rather, whether the database will support the .ORG registry in a > stable, scalable, and highly available manner. > > To: > We believe that the key point relating to databases for the .ORG > redelegation is... whether the database will support the .ORG > registry in a stable, scalable, and highly available manner. > > --======-- > > That's all I see for now... > > Thanks, > > Shane McChesney > President, > Wesearch Information Services Inc. > > Site: http://www.wesearchis.com > Weblog: http://www.skippingdot.net > > On Sun, 27 Oct 2002 10:13:21 -0500, Geoff Davidson wrote: > >Good morning! > > > >As requested, I've put together a draft proposal for this > >announcement of the upcoming release. > > > >This is clearly done with an advocacy based sales & marketing spin. > >It follows sales.org's proven 6 'Power Opening©' steps (of course): > >1. Who you are (PGDG) > >2. What you're selling (PostgreSQL) > >3. What's In It for Them (free alternative to commercial solutions) > >4. Why should they believe you (third party quotes/endorsements) > >5. Expectations (changes in this release, making it even better!) > >6. Process (Where to go and get the code or more info) > > > >Feel free to change and improve any of the content as you wish, I'm > >not burdened by any ego issues wrt pride in authorship, even if you > >decide to throw it out and start over ;) > > > >--Geoff > > > >----- > > > >For Immediate Release November 1st, > >2002 > > > >PostgreSQL Global Development Group Announces Version 7.3 > > > >PostgreSQL, the world's most advanced open source database, provides > >solutions for many of the most demanding applications in use today, > >saving business and government millions of dollars each year. The > >PostgreSQL Global Development Group proudly announces that the "best > >is better again" with the release of the freely available PostgreSQL > >v7.3 object-relational database management system (ORDBMS). > > > >With more than 16 years of development by hundreds of the world's > >most generous and brilliant minds from the open source community, > >PostgreSQL continues to make the decision between free software and > >commercial databases "a simple choice between open source or an open > >wallet." Many companies and agencies can no longer afford the high > >costs and constantly changing terms of licensed commercial software > >- making PostgreSQL one of the most highly sought after free > >technologies in the market today. With the release of v7.3 the > >decision to choose PostgreSQL will be even easier. > > > >Here is what some current PostgreSQL users have gone on record to > >say about this technology: > > > >"We believe that the key point relating to databases for the .ORG > >redelegation is not which database the operator is using, but, > >rather, whether the database will support the .ORG registry in a > >stable, scalable, and highly available manner. > >...over a year of experience...clearly demonstrates that the > >PostgreSQL database used by Afilias performs at the level of > >reliability and availability required for the mission critical > >operations of a global gTLD registry." Internet Society (ISOC) > > > >"PostgreSQL has scaled perfectly with our rapidly expanding > >business, and we recommend it over every other DB." TrustCommerce, > >California > > > >"PgMarket has been developed around PostgreSQL because of its > >unmatched performance, features, price, and scalability. It is the > >best possible database for enterprise e-commerce." Fitcom srl, Italy > > "PostgreSQL provided sales.org with a solution that was $70,000 > >less expensive to create, and over 70% lower in cost to operate and > >maintain than any of the commercial DBMS offerings we looked at." > >sales.org Inc., Toronto > > > >"PostgreSQL handles virtually all the standard SQL constructs. > > > >It is easy (relatively speaking) to administer, it is fast, it is > >efficient, it has a great API, and it supports ODBC, why would you > >choose something else?" Mohawk Software, Massachusetts > > > >"... selected PostgreSQL as one of the key components for their > >solution, relying on the power and extensibility of the database > >even under heavy load." Vanten, K.K., Tokyo > > > > > >Additions & improvements in Version 7.3 release include: > > > >SCHEMAS Schemas allow users to create objects in their own namespace > >so two people or applications can have tables with the same name. > >There is also a public schema for shared tables. > >Table/index creation can be restricted by removing permissions on > >the public schema > > > >Drop Column Now supports ALTER TABLE ... DROP COLUMN functionality. > > > >Table Functions Functions returning multiple rows and/or multiple > >columns are now much easier to use than before. The "table function" > >can be called in the SELECT FROM clause, treating its output like a > >table. Also, plpgsql functions can now return sets. > > > >Prepared Queries For performance, PostgreSQL now supports prepared > >queries. > > > >Dependency Tracking PostgreSQL now records object dependencies, > >which allows improvements in many areas. > > > >Privileges Functions & procedural languages now have privileges. > >People running these can take on the privileges of their creators. > > > >Multibyte/Locale Both multibyte and locale are now always enabled. > > > >Logging A variety of logging options have been enhanced. > > > >Interfaces A large number of interfaces have been moved to > >http://gborg.postgresql.org where they can be developed and released > >independently. > > > >Functions/Identifiers By default, functions can now take up to 32 > >parameters, and identifiers can be up to 63 bytes long. > > > >Along with many many more enhancements, bug fixes and performance > >related changes from v7.2 ... > > > >Source for this release is available on all mirrors under: > >/pub/source/v7.3 > > > >More information on PostgreSQL is available on the project websites > >mirrored worldwide through: http://www.postgresql.org > > > >A complete list of changes in v7.3 can be found in the HISTORY > > > >file, included with the release, or available from all ftp mirrors > >as: /pub/README.v7_3 > > > >Marc G. Fournier Co-ordinator PostgreSQL Global Development Group > > > >---------------------------(end of broadcast) > >------------------------ > >---
Just as a note, we have *at least* 2 weeks to hash this out, before I need to send the release out, so this isn't something that needs to be rushed and finished by Monday ... On Sun, 27 Oct 2002, Geoff Davidson wrote: > Shane, thank you - those are great catches and suggestions. > > Josh Berkus raised some serious concerns about the focus, > so there are some larger decisions on whether it should go > forward in this form with some additions and changes that > will help it with the press that he knows, or if it needs to > go through a major rewrite - but your observations are very > relevant for either direction. > > How about: > Version 7.3 improvements make the choice of PostgreSQL an even easier > decision. > (my objective for that sentence is to acknowledge there are other > 'choices', but really only one intelligent 'decision'...) > > I really like the change you suggested wrt the ISOC quote, less > is often more. > > Justin has done a remarkable job in chasing down companies who > are willing to confirm their choice of PostgreSQL, so we've got > much more ammunition - I picked this selection because collectively > it supports the business case for PostgreSQL on performance, price, > scalability, complexity, usability, international installed base, > and diversity of applications supported. > > There is an abundance of advice and disagreement on the length > that a good release should be, to get maximum attention and > exposure. I've found that a word count between 500 and 800 > is usually effective. This one is in the 650 to 700 word range. > > --Geoff > > > Shane McChesney wrote: > > > > Geoff, > > > > Well done, I think this is great. > > > > Minor copy tweaks, suggestions only, hopefully not too pedantic: > > > > --======-- > > > > In this passage, "again" connotes that it wasn't good for a while > > there or something: > > > > From: > > proudly announces that the "best is better again" > > To: > > proudly announces that "The best has gotten even better!" > > > > --======-- > > > > The phrase "decision to choose" sounds off to me: > > > > From: > > With the release of v7.3 the decision to choose PostgreSQL > > To: > > With the release of v7.3 the decision to adopt PostgreSQL > > Or: > > With the release of v7.3 the decision to use PostgreSQL > > Or: > > With the release of v7.3 the decision to try PostgreSQL > > > > --======-- > > > > If we do pare back the # of quotes in this release (saving ammo for > > future releases can't hurt) I'd keep the Afilias one and narrow the > > first sentence thusly: > > > > From: > > We believe that the key point relating to databases for the .ORG > > redelegation is not which database the operator is using, but, > > rather, whether the database will support the .ORG registry in a > > stable, scalable, and highly available manner. > > > > To: > > We believe that the key point relating to databases for the .ORG > > redelegation is... whether the database will support the .ORG > > registry in a stable, scalable, and highly available manner. > > > > --======-- > > > > That's all I see for now... > > > > Thanks, > > > > Shane McChesney > > President, > > Wesearch Information Services Inc. > > > > Site: http://www.wesearchis.com > > Weblog: http://www.skippingdot.net > > > > On Sun, 27 Oct 2002 10:13:21 -0500, Geoff Davidson wrote: > > >Good morning! > > > > > >As requested, I've put together a draft proposal for this > > >announcement of the upcoming release. > > > > > >This is clearly done with an advocacy based sales & marketing spin. > > >It follows sales.org's proven 6 'Power Opening�' steps (of course): > > >1. Who you are (PGDG) > > >2. What you're selling (PostgreSQL) > > >3. What's In It for Them (free alternative to commercial solutions) > > >4. Why should they believe you (third party quotes/endorsements) > > >5. Expectations (changes in this release, making it even better!) > > >6. Process (Where to go and get the code or more info) > > > > > >Feel free to change and improve any of the content as you wish, I'm > > >not burdened by any ego issues wrt pride in authorship, even if you > > >decide to throw it out and start over ;) > > > > > >--Geoff > > > > > >----- > > > > > >For Immediate Release November 1st, > > >2002 > > > > > >PostgreSQL Global Development Group Announces Version 7.3 > > > > > >PostgreSQL, the world's most advanced open source database, provides > > >solutions for many of the most demanding applications in use today, > > >saving business and government millions of dollars each year. The > > >PostgreSQL Global Development Group proudly announces that the "best > > >is better again" with the release of the freely available PostgreSQL > > >v7.3 object-relational database management system (ORDBMS). > > > > > >With more than 16 years of development by hundreds of the world's > > >most generous and brilliant minds from the open source community, > > >PostgreSQL continues to make the decision between free software and > > >commercial databases "a simple choice between open source or an open > > >wallet." Many companies and agencies can no longer afford the high > > >costs and constantly changing terms of licensed commercial software > > >- making PostgreSQL one of the most highly sought after free > > >technologies in the market today. With the release of v7.3 the > > >decision to choose PostgreSQL will be even easier. > > > > > >Here is what some current PostgreSQL users have gone on record to > > >say about this technology: > > > > > >"We believe that the key point relating to databases for the .ORG > > >redelegation is not which database the operator is using, but, > > >rather, whether the database will support the .ORG registry in a > > >stable, scalable, and highly available manner. > > >...over a year of experience...clearly demonstrates that the > > >PostgreSQL database used by Afilias performs at the level of > > >reliability and availability required for the mission critical > > >operations of a global gTLD registry." Internet Society (ISOC) > > > > > >"PostgreSQL has scaled perfectly with our rapidly expanding > > >business, and we recommend it over every other DB." TrustCommerce, > > >California > > > > > >"PgMarket has been developed around PostgreSQL because of its > > >unmatched performance, features, price, and scalability. It is the > > >best possible database for enterprise e-commerce." Fitcom srl, Italy > > > "PostgreSQL provided sales.org with a solution that was $70,000 > > >less expensive to create, and over 70% lower in cost to operate and > > >maintain than any of the commercial DBMS offerings we looked at." > > >sales.org Inc., Toronto > > > > > >"PostgreSQL handles virtually all the standard SQL constructs. > > > > > >It is easy (relatively speaking) to administer, it is fast, it is > > >efficient, it has a great API, and it supports ODBC, why would you > > >choose something else?" Mohawk Software, Massachusetts > > > > > >"... selected PostgreSQL as one of the key components for their > > >solution, relying on the power and extensibility of the database > > >even under heavy load." Vanten, K.K., Tokyo > > > > > > > > >Additions & improvements in Version 7.3 release include: > > > > > >SCHEMAS Schemas allow users to create objects in their own namespace > > >so two people or applications can have tables with the same name. > > >There is also a public schema for shared tables. > > >Table/index creation can be restricted by removing permissions on > > >the public schema > > > > > >Drop Column Now supports ALTER TABLE ... DROP COLUMN functionality. > > > > > >Table Functions Functions returning multiple rows and/or multiple > > >columns are now much easier to use than before. The "table function" > > >can be called in the SELECT FROM clause, treating its output like a > > >table. Also, plpgsql functions can now return sets. > > > > > >Prepared Queries For performance, PostgreSQL now supports prepared > > >queries. > > > > > >Dependency Tracking PostgreSQL now records object dependencies, > > >which allows improvements in many areas. > > > > > >Privileges Functions & procedural languages now have privileges. > > >People running these can take on the privileges of their creators. > > > > > >Multibyte/Locale Both multibyte and locale are now always enabled. > > > > > >Logging A variety of logging options have been enhanced. > > > > > >Interfaces A large number of interfaces have been moved to > > >http://gborg.postgresql.org where they can be developed and released > > >independently. > > > > > >Functions/Identifiers By default, functions can now take up to 32 > > >parameters, and identifiers can be up to 63 bytes long. > > > > > >Along with many many more enhancements, bug fixes and performance > > >related changes from v7.2 ... > > > > > >Source for this release is available on all mirrors under: > > >/pub/source/v7.3 > > > > > >More information on PostgreSQL is available on the project websites > > >mirrored worldwide through: http://www.postgresql.org > > > > > >A complete list of changes in v7.3 can be found in the HISTORY > > > > > >file, included with the release, or available from all ftp mirrors > > >as: /pub/README.v7_3 > > > > > >Marc G. Fournier Co-ordinator PostgreSQL Global Development Group > > > > > >---------------------------(end of broadcast) > > >------------------------ > > >--- > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html >
Marc,
> IMHO, its the non-tech press that needs to be "informed/targetted"
> ... its
> alot easier on the techs if their CTO comes to them and mentioned
> 'this
> RDBMS PostgreSQL that they just read abou that we should
> investigate',
> then for the tech to convince the CTO ... eaiser to implement
> something
> when the higher-ups are pushing for it :)
By "general tech press" I mean, for example, News.com and the
Washingtion Post Business/Tech page. As opposed to "open source
press", such as NewsForge and The Register, who would probably cover us
even if we just forwarded them a mailing list message.
As nice as it might be to get ourselves on the front page of the WST,
it ain't gonna happen until we get a major world government to switch
their operations over to PostgreSQL. And maybe not even then, if
OpenOffice.org is anything to go by (Germany adopted OOo/StarOffice,
and we didn't even get a page 3 blurb in the WST. They are *not*
friendly to Open Source).
My questions are:
1) Who is this press release for?
a) The general tech press
b) the Open Source press
c) PostgreSQL users and customers
d) PostgreSQL Inc. customers
e) all or some of the above
2) Do we want to prepare 2 or more press releases for different target
audiences?
3) Should the PostgreSQL.org press release overlap with PostgreSQL
Inc.'s press release? If so, how?
4) Will we provide advance copies of the press release to other
companies that support PostgreSQL development for them to release to
their customers?
5) Who are our "official press contacts?" Each needs name, phone,
address, e-mail.
6) What should the balance of emphasis between new release features and
general PostgreSQL promotion be in the press release?
7) How much testimonial material should be in this press release, and
how much on the Advocacy web page?
8) Should we include a technical rundown of the new features, or just a
general-audience one? (by my evaluation, Geoff's list falls in the 60%
technical, 40% general audience level)
9) Can we get a programmer quote about the new release? Please?
Of the above, I have strong opinions about a few things:
1) Whether it is this release or not, we should compose a 7.3 press
release targeted to the general tech press.
5) I should not be an official press contact for at least 6 months, as
my name is still strongly associated with OpenOffice.org. Whether
Geoff can be the official press contact depends on the answer to
question 2.
6) As news agencies are interested in *news*, not in products, we
should lead with the new features (and what they mean to the layman)
and trail with general PostgreSQL laudatory stuff. For this release,
we have 3 peices of news-as-new:
a) The 7.3 release
b) We now have a PR group and a PR web page
c) *All* of the applicants for the .ORG registry use either PostgreSQL
or Oracle, de facto making us a direct alternative to Oracle.
7) We should find the 3 best, most relevant quotes and include them,
and put the rest on the web page.
8) General audience only.
As I said before, all of the above is my *personal* opinion; I don't
speak for anyone else.
-Josh Berkus
On Sun, 27 Oct 2002, Josh Berkus wrote: > Marc, > > > IMHO, its the non-tech press that needs to be "informed/targetted" > > ... its > > alot easier on the techs if their CTO comes to them and mentioned > > 'this > > RDBMS PostgreSQL that they just read abou that we should > > investigate', > > then for the tech to convince the CTO ... eaiser to implement > > something > > when the higher-ups are pushing for it :) > > By "general tech press" I mean, for example, News.com and the > Washingtion Post Business/Tech page. As opposed to "open source > press", such as NewsForge and The Register, who would probably cover us > even if we just forwarded them a mailing list message. > > As nice as it might be to get ourselves on the front page of the WST, > it ain't gonna happen until we get a major world government to switch > their operations over to PostgreSQL. And maybe not even then, if > OpenOffice.org is anything to go by (Germany adopted OOo/StarOffice, > and we didn't even get a page 3 blurb in the WST. They are *not* > friendly to Open Source). > > My questions are: > 1) Who is this press release for? > a) The general tech press > b) the Open Source press IMHO, the above two ... > c) PostgreSQL users and customers > d) PostgreSQL Inc. customers the above two are "already informed" ... > 2) Do we want to prepare 2 or more press releases for different target > audiences? I don't believe so ... there should be "A Press Release" which is targeted to 1a/1b ... and a 'Release Announcements' which is target'd towards 1c .. > 3) Should the PostgreSQL.org press release overlap with PostgreSQL > Inc.'s press release? If so, how? Not sure why PostgresQL, Inc would do a seperate press release, we aren't releasing anything new ... all we should be targetting here is PostgreSQL.Org's v7.3 release ... > 4) Will we provide advance copies of the press release to other > companies that support PostgreSQL development for them to release to > their customers? I don't believe so ... is there any reason why such companies aren't involved with this list in the first place? > 6) What should the balance of emphasis between new release features and > general PostgreSQL promotion be in the press release? We need to somehow emphasis that what "the rest" are touting as their new features are what we've always had, while promoting our new features ... which could be hard ... I'm tired of hearing about how great MySQL is because it has transactions now, while we've always had it ... we need to make ppl aware that we've always had those features and that they have been well tested over the past several years ... > 7) How much testimonial material should be in this press release, and > how much on the Advocacy web page? I would think you'd want very little in the press release ... > 8) Should we include a technical rundown of the new features, or just a > general-audience one? (by my evaluation, Geoff's list falls in the 60% > technical, 40% general audience level) General audience one ... > 9) Can we get a programmer quote about the new release? Please? Tom, I think you are well overdue for being quoted, no? :)
On Sun, Oct 27, 2002 at 02:14:10PM -0800, Josh Berkus wrote:
> By "general tech press" I mean, for example, News.com and the
> Washingtion Post Business/Tech page. As opposed to "open source
> press", such as NewsForge and The Register, who would probably cover us
> even if we just forwarded them a mailing list message.
In that case, I think we can safely say that the general tech world
doesn't really know what PostgreSQL is. Oracle's attempt to attack
PostgreSQL during the .org bids was either totally uninformed about
what PostgreSQL is; or, it was _not_ uninformed, but it was relying
on the general lack of knowledge. One way or another, it was
obviously relying on the general impresison that free RDBMS == MySQL
(and that in a version without, e.g., InnoDB tables). This is just
an observation, mind you; I barely even read the tech press, never
mind understand what is likely to attract attention from them.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
On Sun, Oct 27, 2002 at 04:03:47PM -0500, Geoff Davidson wrote:
> scalability, complexity, usability, international installed base,
Again, I can say that, from our experience in the .org bid, installed
base really sways a lot of people. Never mind the relevance of such
a consideration to whether it is the right tool for the job. Many
arguments in favour of not picking the ISOC/PIR bid relied on the
premise, "Everyone uses Oracle, so it must be the right thing to
use." And Gartner was clear that the big liability they thought
PostgreSQL represented was that it was untried, even though we've
been using it for a year in the very same application.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
On Sun, 2002-10-27 at 18:04, Marc G. Fournier wrote: > On Sun, 27 Oct 2002, Josh Berkus wrote: > > > Marc, > > > > > IMHO, its the non-tech press that needs to be "informed/targetted" > > > ... its > > > alot easier on the techs if their CTO comes to them and mentioned > > > 'this > > > RDBMS PostgreSQL that they just read abou that we should > > > investigate', > > > then for the tech to convince the CTO ... eaiser to implement > > > something > > > when the higher-ups are pushing for it :) > > > > By "general tech press" I mean, for example, News.com and the > > Washingtion Post Business/Tech page. As opposed to "open source > > press", such as NewsForge and The Register, who would probably cover us > > even if we just forwarded them a mailing list message. > > > > As nice as it might be to get ourselves on the front page of the WST, > > it ain't gonna happen until we get a major world government to switch > > their operations over to PostgreSQL. And maybe not even then, if > > OpenOffice.org is anything to go by (Germany adopted OOo/StarOffice, > > and we didn't even get a page 3 blurb in the WST. They are *not* > > friendly to Open Source). > > > > My questions are: > > 1) Who is this press release for? > > a) The general tech press > > b) the Open Source press > > IMHO, the above two ... > I agree with Mark on this one. I don't think we can expect to get on the front page on many tech sites, but it should give us some exposure in places we need to reach, and might help PostgreSQL make the next "database shootout" article that gets published by those tech sites. > > c) PostgreSQL users and customers > > d) PostgreSQL Inc. customers > > the above two are "already informed" ... > > > 2) Do we want to prepare 2 or more press releases for different target > > audiences? > > I don't believe so ... there should be "A Press Release" which is targeted > to 1a/1b ... and a 'Release Announcements' which is target'd towards 1c .. > > > 3) Should the PostgreSQL.org press release overlap with PostgreSQL > > Inc.'s press release? If so, how? > > Not sure why PostgresQL, Inc would do a seperate press release, we aren't > releasing anything new ... all we should be targetting here is > PostgreSQL.Org's v7.3 release ... this is needed clarification, as Geoff said "this isn't .Inc's press release which I interpreted as meaning that PostgreSQL Inc would also be doing a press release. If not then that makes it less confusing for those of us here. > > > 4) Will we provide advance copies of the press release to other > > companies that support PostgreSQL development for them to release to > > their customers? > > I don't believe so ... is there any reason why such companies aren't > involved with this list in the first place? > Having no real affiliation with PostgreSQL Inc, I want to second Mark's notion here. > > 6) What should the balance of emphasis between new release features and > > general PostgreSQL promotion be in the press release? > > We need to somehow emphasis that what "the rest" are touting as their new > features are what we've always had, while promoting our new features ... > which could be hard ... I'm tired of hearing about how great MySQL is > because it has transactions now, while we've always had it ... we need to > make ppl aware that we've always had those features and that they have > been well tested over the past several years ... > I think we all get annoyed by that, but we have to be careful not to dwell on it or it will seem like whining. > > 7) How much testimonial material should be in this press release, and > > how much on the Advocacy web page? > > I would think you'd want very little in the press release ... Again I agree. I would rather have a blurb that says "postgresql has been running the .info domain for over 1 year, and recently was chosen over Oracle to run the .org domain as well" instead of the quote from the ISOC. I just think it paints a much clearer picture. > > > 8) Should we include a technical rundown of the new features, or just a > > general-audience one? (by my evaluation, Geoff's list falls in the 60% > > technical, 40% general audience level) > > General audience one ... If possible maybe some 1 liners explaining how a given feature helps the potential end-user. Compare the SCHEMAS vs. Table Functions explanations. Personally I think the table functions are going to be much more important to me than schema support, but reading the release it's easier to see why someone might want to use schemas than the table functions. > > > 9) Can we get a programmer quote about the new release? Please? > > Tom, I think you are well overdue for being quoted, no? :) > Robert Treat
On 28 Oct 2002, Robert Treat wrote: > this is needed clarification, as Geoff said "this isn't .Inc's press > release which I interpreted as meaning that PostgreSQL Inc would also be > doing a press release. If not then that makes it less confusing for > those of us here. Geoff follow'd this one up by stating that our only press release on the subject would be one of a congratulatory nature ... > > I would think you'd want very little in the press release ... > > Again I agree. I would rather have a blurb that says "postgresql has > been running the .info domain for over 1 year, and recently was chosen > over Oracle to run the .org domain as well" instead of the quote from > the ISOC. I just think it paints a much clearer picture. Not sure how/if to say, but it is kinda nice that considering that OpenSource has been running the root name servers, the registrars themselves are finally catching up :)