Re: Release, 3rd draft - Mailing list pgsql-advocacy

From Josh Berkus
Subject Re: Release, 3rd draft
Date
Msg-id 200510031313.37412.josh@agliodbs.com
Whole thread Raw
In response to Re: Release, 3rd draft  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: Release, 3rd draft
License blurb (was: Release, 3rd draft)
Re: Release, 3rd draft
List pgsql-advocacy
Jim, Josh, Lance:

> I would say ignore the number of beta downloads and focus on the number
> of community members assisting.

What's the number of unique posters to pgsql-bugs and pgsql-hackers since
beta started?   Can anyone get me that number?

> Well, it's inconsistent with the usage in the first paragraph (IN/OUT).
> And usually when I see a reference to the *concept* (which is what I'd
> say the PR is), it's usually called IN/OUT as an umbrella term for
> IN/OUT/INOUT.

OK.

> ...the query planner is now able to entirely avoid scanning tables that
> it knows will not have any data to satisfy a query. This feature, called
> Constraint Elimination, utilizes constraints placed on tables to decide
> if they have any valid data for a given query. This is the foundation
> upon which table partitioning can be built.

Too technical.  And we don't want to imply that we *don't* have table
partitioning; we have it as much as MySQL or Ingres has.   Basically this
blurb is a careful balance between saying "We have Table Partitioning!"
and overhyping the feature.

> In any case, I definately think we need to raise awareness of the
> licensing issue.

Can you draft a short (4-6 line) paragraph for inclusion in the web-based
presskit (NOT the release)?   WITHOUT saying anything bad about the GPL?

--Josh

--
__Aglio Database Solutions_______________
Josh Berkus               Consultant
josh@agliodbs.com     www.agliodbs.com
Ph: 415-752-2500    Fax: 415-752-2387
2166 Hayes Suite 200    San Francisco, CA

pgsql-advocacy by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Release, 3rd draft
Next
From: "Lance Obermeyer"
Date:
Subject: Re: Release, 3rd draft