Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)
Дата
Msg-id 603c8f070902251956s16eee4a7l495d75d3ddccc78a@mail.gmail.com
обсуждение исходный текст
Ответ на Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)
Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)
Список pgsql-hackers
On Tue, Jan 27, 2009 at 11:23 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dave Page <dpage@pgadmin.org> writes:
>> On Tue, Jan 27, 2009 at 3:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> I already pointed out some pretty serious problems with the updatable
>>> views patch.  Are you claiming they are trivial to fix?
>
>> Not at all. I think the deferral of that particular patch is the
>> correct thing to do because there are confirmed, real problems with it
>> that are not realistic to fix in an appropriate timeframe for the
>> release. The primary case that I'm objecting to is HS which you've
>> been saying will take 10 - 12 months to complete having by your own
>> admission not looked at the code or followed the discussion
>> particularly closely.
>
> Well, perhaps I'm being pessimistic, or perhaps you're being
> optimistic.  What is undeniable fact is that HS will not be committable
> this week, which will make it three months since feature freeze.
> As for when it *will* be committable --- Heikki is saying two weeks
> if no new problems crop up, but given the rate at which new problems
> have been found so far, what are the odds of that?  We've seen this
> movie before.
>
> Since it's going to take us two weeks to clean up the other loose ends
> anyway, there's no harm in letting Simon and Heikki try to complete the
> patch by then.  But I'll happily lay a side bet with you about what the
> situation will be two weeks from now.

I think Tom wins this bet, since it's now been four weeks.  In fact,
he was being optimistic: the loose ends aren't cleaned up either
(based on a review of the wiki, we're about half way there: six
patches have been committed in the intervening time and seven remain
in the queue).

...Robert


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Proposed Patch to Improve Performance of Multi-BatchHash Join for Skewed Data Sets
Следующее
От: KaiGai Kohei
Дата:
Сообщение: Updates of SE-PostgreSQL 8.4devel patches (r1627)