Re: Schedule for 8.1 feature freeze

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To:
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schedule for 8.1 feature freeze
Date: 2005-06-21 09:02:07
Message-ID: Pine.GSO.4.63.0506211252340.19683@ra.sai.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> -----Original Message-----
>> From: pgsql-hackers-owner(at)postgresql(dot)org
>> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
>> Sent: 21 June 2005 05:04
>> To: PostgreSQL-development
>> Subject: [HACKERS] Schedule for 8.1 feature freeze
>>
>> We have addressed all the open issues for 8.1 except for auto-vacuum,
>> which Alvaro is working on, so I think we are ready for a
>> feature freeze
>> on July 1.

Bruce, we're working on GiST concurrency which is based on GiST recovery
code already submitted. Hopefully, we'll submit patch before July 1.
There is also one problem we already discussed - we have no gist opclasses
in core we could use for regression tests ! Probably, it's a time we need
to add some opclasses from intarray or rtree_gist to core ?

btw, there was a noise about funding of our work, but I've contacted only
with PostGis guys about real contribution. I'm just wondered if any
commercial clones do really understand the importance of our work. Should
I write some explanation what're recovery and concurrency for GiST ?

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alfranio Correia Junior 2005-06-21 09:35:32 Re: HOOKS for Synchronous Replication
Previous Message Alfranio Correia Junior 2005-06-21 08:36:10 Re: HOOKS for Synchronous Replication