Skip site navigation (1) Skip section navigation (2)

Re: First CommitFest: July 15th

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First CommitFest: July 15th
Date: 2009-07-03 02:16:41
Message-ID: 603c8f070907021916n5fbe8c4dt4cbb8f040531cb2a@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jul 2, 2009 at 3:42 PM, Zdenek Kotala<Zdenek(dot)Kotala(at)sun(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2009-07-03 02:45:52
Subject: Re: [PATCH] SE-PostgreSQL Updates rev.2096
Previous:From: Robert HaasDate: 2009-07-03 02:07:24
Subject: Re: Synch Rep: direct transfer of WAL file from the primary to the standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group