Обсуждение: Releasing an alpha for CF2

Поиск
Список
Период
Сортировка

Releasing an alpha for CF2

От
Josh Berkus
Дата:
Hackers,

I'd really like us to release an alpha version based on the finished
CF2.  There have been a number of major features added to PostgreSQL
prior to this CF -- including Haas's performance improvements and range
types -- which we really want at least some users to test early.

Would it be possible to do an alpha release?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


Re: Releasing an alpha for CF2

От
Alexander Korotkov
Дата:
On Wed, Nov 9, 2011 at 12:56 AM, Josh Berkus <josh@agliodbs.com> wrote:
I'd really like us to release an alpha version based on the finished
CF2.  There have been a number of major features added to PostgreSQL
prior to this CF -- including Haas's performance improvements and range
types -- which we really want at least some users to test early.

People trying range types are likely to try indexes on them. GiST on range types implementation in head have some limitations:
1) Full index scan for "column <@ const" case.
2) Absence of selectivity estimation functions for &&, <@, @> cause no GiST index usage until turning enable_seqscan to off.

IMHO, it would be nice to release alpha version with range types without these limitations. I'm going to finish my patch for GiST on range types in couple of days. Concerning selectivity estimation, possible solution is to create some constant estimations with lower selectivity, which make planner use corresponding index by default (like we've for geometric datatypes).

------
With best regards,
Alexander Korotkov.  

Re: Releasing an alpha for CF2

От
Josh Berkus
Дата:
Alexander,

> People trying range types are likely to try indexes on them. GiST on range
> types implementation in head have some limitations:

... it's an alpha.  There will always be one more patch.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


Re: Releasing an alpha for CF2

От
Robert Haas
Дата:
On Tue, Nov 8, 2011 at 3:56 PM, Josh Berkus <josh@agliodbs.com> wrote:
> I'd really like us to release an alpha version based on the finished
> CF2.  There have been a number of major features added to PostgreSQL
> prior to this CF -- including Haas's performance improvements and range
> types -- which we really want at least some users to test early.
>
> Would it be possible to do an alpha release?

Well, we discussed this not long ago, and the conclusion was that we
could do an alpha release if and when someone was willing to write
release notes.  I suggested that it would make sense to do our first
alpha after CF3, and that's still pretty much how I feel about it.  If
we're lucky, maybe we can twist Bruce's arm into doing it.
Regardless, I don't think there's much time in trying to squeeze it
into the week remaining before CF3, though; anything we write now will
be obsolete almost as soon as it's written.

An interesting question is this: What fraction of what is ultimately
going to end up in this release is done now, or what fraction will be
done by the end of CF3?  Last time around, all the major features kind
of fell on our head in January.  But some of those - like SSI and sync
rep - were things that we knew to be coming long in advance.  I know
various people are working on patches to do various things, but the
only outstanding thing that sticks out in my mind as an outstanding
"big feature" patch is Alvaro's work on foreign key locks.  I'm sure
there must be others...  but I'm not sure how many.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


Re: Releasing an alpha for CF2

От
Greg Smith
Дата:
On 11/08/2011 09:31 PM, Robert Haas wrote:
> I know various people are working on patches to do various things, but the
> only outstanding thing that sticks out in my mind as an outstanding
> "big feature" patch is Alvaro's work on foreign key locks.  I'm sure
> there must be others...  but I'm not sure how many.
>    

Along with that, there's a lot of potential for ripple from the "Command 
Triggers" patch Dimitri just submitted today.  That's already 
approaching 3000 lines of code and he's still going on it.  I've been 
sniffing around recently looking for troublesome patches, under the 
assumption I'll be running the CF next week, and those two are the ones 
I've been most concerned about.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us