Re: Hot Standby 0.2.1 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Hot Standby 0.2.1
Date
Msg-id 200910091809.n99I9G715044@momjian.us
Whole thread Raw
In response to Re: Hot Standby 0.2.1  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan wrote:
> 
> 
> Robert Haas wrote:
> > But at least for simple features I think that there would be a value 
> > in separating the patch author's work from the committer's adjustments.
> >
> >
> 
> That is just going to make life harder for committers.
> 
> There are plenty of things with my name on them that are not exactly 
> what I submitted. I think that's true of just about everybody. Mostly 
> things changed hae improved, but not always. I don't think we should be 
> too proprietary about patches. As far as I'm concerned, credit goes to 
> the submitter and blame if any to the committer.

Agreed.  

Simon is right that if only his name is on the commit, there is an
assumption that the committer made no changes, or only cosmetic ones.
For hot standby, I think the committer is making significant changes
(that could lead to bugs) and hence the committer's name should be in
the commit.  Sometimes we say "adjusted by" committer, but in this case
I think Heikki is doing more than adjustmants --- nothing wrong with
that --- it should just be documented in the commit message.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Hot Standby 0.2.1
Next
From: Markus Wanner
Date:
Subject: Re: Concurrency testing