Re: Postgres alpha testing docs and general test packs - Mailing list pgsql-general

From Thom Brown
Subject Re: Postgres alpha testing docs and general test packs
Date
Msg-id bddc86150910280713l50296545k42f68222c2162b35@mail.gmail.com
Whole thread Raw
In response to Re: Postgres alpha testing docs and general test packs  (Adrian Klaver <aklaver@comcast.net>)
Responses Re: Postgres alpha testing docs and general test packs
Re: Postgres alpha testing docs and general test packs
List pgsql-general
2009/10/28 Adrian Klaver <aklaver@comcast.net>:
>> Entirely new features are easier to deal with though.  I still would,
>> however, want something like a detailed version of Josh's post which
>> breaks down where the changes have occurred.  It seems quite scattered
>> and unclear at the moment.
>>
>> Thom
>
> http://developer.postgresql.org/pgdocs/postgres/release-8-5.html

Thanks Adrian.  I just wasn't looking hard enough obviously :)  That
list still doesn't appear to be explicit enough though as we have
"Multiple improvements in contrib/hstore, including raising limits on
keys and values".  What exactly is meant by limit, what was this limit
before and what has it been raised to?

Similarly: "Fix encoding handling in binary input function of xml
type."  What was the problem before?

And: "Allow the collection of statistics on sequences".  How would
your average end-user see whether these statistics are being colelcted
on sequences?  And are these statistics actually used anywhere yet?

I'm not really asking for the answer to those questions.  I'm pointing
out that it isn't clear (at least to me) how to determine what exactly
has been fixed in order to test it.  This doesn't apply to everything
listed as some of it is quite clear, like "pg_dump/pg_restore --clean
now drops large objects."

Thanks

Thom

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Postgres alpha testing docs and general test packs
Next
From: Peter Hunsberger
Date:
Subject: Re: still on joining array/inline values was and is: design, ref integrity and performance