Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Date
Msg-id 201107121413.p6CEDgI03933@momjian.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Excerpts from Magnus Hagander's message of mar jul 12 09:34:56 -0400 2011:
> 
> > > Agreed.  On one level I like the sponsor message, but on the other
> > > having "Sponsored by RedHat" on every Tom Lane item will get tiring.
> > > ;-)
> > >
> > > Can we add text if the employer is _not_ the feature sponsor?
> > 
> > That would be quite unfair to those who *do* employ committers....
> > Basically you'd get credit only if you didn't employ a committer.
> 
> Well, that has worked well for my case -- I haven't ever credited my
> employer, only those that have specifically hired us for a particular
> patch.  My employer gets a lot of "credit" in the form of email
> signatures, like the one below ;-)
> 
> But I see your point and I will stick to whatever policy we come up with
> (assuming we come up with one).
> 
> > This all becomes much easier if we keep the ads out of the commit
> > messages, and stick to the technical side there. And find another
> > venue for the other credit.
> 
> I'm open to ideas.

Agreed.  I am not firm either way on the issue;  I was just throwing out
a suggestion.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: per-column generic option
Next
From: Magnus Hagander
Date:
Subject: Re: marking old branches as no longer maintained