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

From Jim Nasby
Subject Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
Date
Msg-id FB86FC42-0E5D-4C9E-87BA-9616686517FB@nasby.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID
List pgsql-hackers
On Jul 12, 2011, at 11:30 AM, Joshua D. Drake wrote:
>>> 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.
>
> I think the commit log isn't actually useful for the "advertising" portion of this. Users don't read commit logs for
themost part. However, it is an easy way for people who are writing release notes, press releases, etc... to find the
information.
>
> Is it a good place for the information? No.
>
> Is it the easiest place to store it until somebody steps up and creates a proper way to track it so that it can be
desimnatedproperly throughout the community? Probably. 
>
> We do need a way to track this information.
+1 on everything Josh said.

Does git allow for additional commit fields? That would allow for easy tracking without much additional burden on
committers.
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net




pgsql-hackers by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: psql: bogus descriptions displayed by \d+
Next
From: Tom Lane
Date:
Subject: Re: Re: patch review : Add ability to constrain backend temporary file space