Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Date: 2011-07-03 18:51:54
Message-ID: 1309719114.7252.11.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On tor, 2011-06-30 at 15:09 -0400, Alvaro Herrera wrote:
> Robert Hass (whose name I misspelled in the commit message above) just
> mentioned to me (in an answer to my apologizing about it) that he
> didn't think that mentioning sponsors for patch development was a good
> idea.
>
> I don't think we have a policy for this, but I have done it for some
> time now and nobody has complained, so I sort of assumed it was okay.
> Besides, some of the people pouring the money in does care about it;
> moreover, it provides a little incentive for other companies that
> might also be in a position to fund development but lack the "peer
> approval" of the idea, or a final little push.

I think commit messages should be restricted to describing what was
changed and who is responsible for it. Once we open it for things like
sponsorship, what's to stop people from adding personal messages, what
they had for breakfast, "currently listening to", or just selling
advertising space in each commit message for 99 cents?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Magnus Hagander 2011-07-03 19:06:48 Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Previous Message Tom Lane 2011-07-03 17:55:38 pgsql: Make distprep and *clean build targets recurse into all subdirec

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2011-07-03 18:54:45 Re: Full GUID support
Previous Message Michael Gould 2011-07-03 18:42:33 Full GUID support