Re: First CommitFest: July 15th

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: First CommitFest: July 15th
Дата
Msg-id 603c8f070907021916n5fbe8c4dt4cbb8f040531cb2a@mail.gmail.com
обсуждение исходный текст
Ответ на Re: First CommitFest: July 15th  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Ответы Re: First CommitFest: July 15th  (Peter Eisentraut <peter_e@gmx.net>)
Re: First CommitFest: July 15th  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Список pgsql-hackers
On Thu, Jul 2, 2009 at 3:42 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote:
>
> Josh Berkus píše v st 01. 07. 2009 v 17:21 -0700:
>> Folks,
>>
>> There's been a lot of discussion/argument around how to handle the last
>> commitfest, but there seems to be a total consensus that we want to have
>> the first CF on July 15th.
>
> Can we add flags like bump catalog version, bump page layout version,
> modify AM for each patch? It should help to track pg_upgrade changes.

That's not a bad idea, and it wouldn't be hard to add various flags
and things to the CommitFest app I wrote, but how would we maintain
the information and keep it correct?  It seems like there might be a
danger that patch authors wouldn't know whether or not they were doing
those things.  Also, how would we handle changes by committers, who
don't always go through the CommitFest process?

Not sure of the answers here, just thinking out loud.

...Robert


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Synch Rep: direct transfer of WAL file from the primary to the standby