Thread: Press Release: new draft, PressKit.html

Press Release: new draft, PressKit.html

From
Josh Berkus
Date:
All:

So, third draft is up on CVS, along with a first draft of
presskit82.html.en (the extended presskit page).  They are also available
at:
http://pgfoundry.org/docman/view.php/1000047/233/release82.zip

Please comment.  Especially:

Release:
    -- is the order of the features listed OK?
    -- are the wording changed to the SQL 2003 features adequate?
    -- any other corrections?

PressKit:
    -- features listed: I pretty much threw in the kitchen sink with this one.
Please suggest features to subtract/add.
    -- pgfoundry stuff: surely there are projects other than pgPool, Full
Disjunctions and PL/Java worth mentioning.  Suggestions?
    --links: are all of the links still appropriate?

Feedback wanted; I plan to finish these drafts by next Friday.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

Re: Press Release: new draft, PressKit.html

From
Chris Mair
Date:
> Feedback wanted; I plan to finish these drafts by next Friday.


   "blah blah blah blah" said Theo Scholossenagle, "3 tb postgresql
   database, really need some 8.2 stuff."

The name should be Theo Schlossnagle, I think...

Bye :)
Chris.





Re: Press Release: new draft, PressKit.html

From
Yourfriend
Date:


On 9/25/06, Yourfriend <doudou586@gmail.com> wrote:
<!-- BEGIN page_title_block -->
PostgreSQL 8.1 Press Kit
<!-- END page_title_block -->

<h1>PostgreSQL 8.1 Press Kit</h1>

Should the title and header be changed to 8.2 ?




Daojing.Zhou on 2006/09/25


Sorry to Chris, the mail should send to Josh Berkus.

Re: Press Release: new draft, PressKit.html

From
"Harald Armin Massa"
Date:
Josh,

I like the structure of the features and especially how you formulated the part with SQL 2003!
I am no native speaker of the English language. For me this sentence is very very hard to digest:

"""Performance improvements: version 8.2 improves performance around 20%
overall in high-end OLTP systems and even larger gains in data warehousing
efficiency""

I had to read it around 3 times trying to get it; I was desperately missing a verb for the "larger gains".
My recommendation is to split it into 2 sentences and add another verb; at least an auxiliary one; that will make it also easier splitable for journalists:

"""Performance improvements: version 8.2 improves performance around 20%
overall in high-end OLTP systems. There are even larger gains in data warehousing
efficiency."""


You explain OLTP further down:

"Online Index Builds: lets OLTP (online transactional processing)
applications update tables while they are being indexed."

I recommend to explain OLTP at its first occurence (counting "first" on reading top down), rather than on its second.

My latin-german-english comma-setting sense recommends another "," before include:

"""Advanced database features, being offered in PostgreSQL 8.2 before any other
major database system, include:"""

because that "include" belongs to the "Advanced db features", and "being....system" is an insertion.

and I think the last "," here can be dropped:

"""The changes include faster in-memory and on-disk
sorting, better multi-processor scaling, better planning of partitioned
data queries, faster bulk loads, and vastly accelerated outer joins."""

because "and" allready counts as separator between the elements of this list.

Best wishes,

Harald


--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Reinsburgstraße 202b
70197 Stuttgart
0173/9409607
-
Python: the only language with more web frameworks than keywords.
http://groups.google.de/group/comp.lang.python/browse_thread/thread/285b9adeec188fb2

Re: Press Release: new draft, PressKit.html

From
Oleg Bartunov
Date:
Josh,

<li>Major TSearch2 Improvements: including new dictionary and thesaurus support,
  and GIN indexing.</li>

should be

<li>Major TSearch2 Improvements: UTF-8, thesaurus dictionary, query rewriting
support and GIN indexing.</li>



On Fri, 22 Sep 2006, Josh Berkus wrote:

> All:
>
> So, third draft is up on CVS, along with a first draft of
> presskit82.html.en (the extended presskit page).  They are also available
> at:
> http://pgfoundry.org/docman/view.php/1000047/233/release82.zip
>
> Please comment.  Especially:
>
> Release:
>     -- is the order of the features listed OK?
>     -- are the wording changed to the SQL 2003 features adequate?
>     -- any other corrections?
>
> PressKit:
>     -- features listed: I pretty much threw in the kitchen sink with this one.
> Please suggest features to subtract/add.
>     -- pgfoundry stuff: surely there are projects other than pgPool, Full
> Disjunctions and PL/Java worth mentioning.  Suggestions?
>     --links: are all of the links still appropriate?
>
> Feedback wanted; I plan to finish these drafts by next Friday.
>
>

     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

Re: Press Release: new draft, PressKit.html

From
"Joshua D. Drake"
Date:
Oleg Bartunov wrote:
> Josh,
>
> <li>Major TSearch2 Improvements: including new dictionary and thesaurus
> support,
>  and GIN indexing.</li>
>
> should be
>
> <li>Major TSearch2 Improvements: UTF-8, thesaurus dictionary, query
> rewriting support and GIN indexing.</li>
>

<li>Major TSearch2 Improvements: UTF-8, thesaurus, query
rewriting support and GIN indexing.</li>

The word dictionary is redundant...

Sincerely,

Joshua D. Drake

--

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/



Re: Press Release: new draft, PressKit.html

From
Oleg Bartunov
Date:
On Mon, 25 Sep 2006, Joshua D. Drake wrote:

> Oleg Bartunov wrote:
>> Josh,
>>
>> <li>Major TSearch2 Improvements: including new dictionary and thesaurus
>> support,
>>  and GIN indexing.</li>
>>
>> should be
>>
>> <li>Major TSearch2 Improvements: UTF-8, thesaurus dictionary, query
>> rewriting support and GIN indexing.</li>
>>
>
> <li>Major TSearch2 Improvements: UTF-8, thesaurus, query
> rewriting support and GIN indexing.</li>
>
> The word dictionary is redundant...

agree

>
> Sincerely,
>
> Joshua D. Drake
>
>

     Regards,
         Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

Re: Press Release: new draft, PressKit.html

From
Josh Berkus
Date:
Harald, Oleg, Josh, DouDou,

Thanks for corrections.  Updated in CVS.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

Re: Press Release: new draft, PressKit.html

From
Jim Nasby
Date:
On Sep 25, 2006, at 3:13 AM, Harald Armin Massa wrote:
> I like the structure of the features and especially how you
> formulated the part with SQL 2003!
> I am no native speaker of the English language. For me this
> sentence is very very hard to digest:
>
> """Performance improvements: version 8.2 improves performance
> around 20%
> overall in high-end OLTP systems and even larger gains in data
> warehousing
> efficiency""
>
> I had to read it around 3 times trying to get it; I was desperately
> missing a verb for the "larger gains".
> My recommendation is to split it into 2 sentences and add another
> verb; at least an auxiliary one; that will make it also easier
> splitable for journalists:

"...OLTP systems with even larger..."

> """Performance improvements: version 8.2 improves performance
> around 20%
> overall in high-end OLTP systems. There are even larger gains in
> data warehousing
> efficiency."""

Or that...

> You explain OLTP further down:
>
> "Online Index Builds: lets OLTP (online transactional processing)
> applications update tables while they are being indexed."
>
> I recommend to explain OLTP at its first occurence (counting
> "first" on reading top down), rather than on its second.

+1

> My latin-german-english comma-setting sense recommends another ","
> before include:
>
> """Advanced database features, being offered in PostgreSQL 8.2
> before any other
> major database system, include:"""
>
> because that "include" belongs to the "Advanced db features", and
> "being....system" is an insertion.

Actually, the whole thing sounds awkward to me. How about...

This release also adds a number of advanced database features that
have yet to be included in any other major database system, including:

> and I think the last "," here can be dropped:
>
> """The changes include faster in-memory and on-disk
> sorting, better multi-processor scaling, better planning of
> partitioned
> data queries, faster bulk loads, and vastly accelerated outer
> joins."""
>
> because "and" allready counts as separator between the elements of
> this list.

AFAIK either is acceptable, at least in US-ian english. Personally, I
prefer keeping the comma.

"which started at the University of California at Berkeley" - Is
there another acceptable name, maybe University of California,
Berkeley? The double-use of "at" so close together sounds awkward to me.
--
Jim Nasby                                    jimn@enterprisedb.com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)